You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently codegenerator on Z checks if the platform has vector facilities installed and sets up the correct flag that is used throughout the codebase in both OMR and OpenJ9. ATM these checks are done in OpenJ9 weirdly in while constructing the Private Linkage [1]. This kind of general platform checks should be migrated to OMR, although simply moving them to OMRGenerator leads to segmentation fault in JIT codegen. I am opening up this issue to keep track and document the reasons behind those failure. More details can be found in [2]
While constructing a code generator object, check for vector facility
and set appropriate options. This check was done previously in
S390PrivateLinkage in OpenJ9, which would be incorrect place to do so.
Fixes: eclipse#6572
Signed-off-by: Rahil Shah <rahil@ca.ibm.com>
While constructing a code generator object, check for vector facility
and set appropriate options. This check was done previously in
S390PrivateLinkage in OpenJ9, which would be incorrect place to do so.
Fixes: eclipse#6572
Signed-off-by: Rahil Shah <rahil@ca.ibm.com>
Currently codegenerator on Z checks if the platform has vector facilities installed and sets up the correct flag that is used throughout the codebase in both OMR and OpenJ9. ATM these checks are done in OpenJ9 weirdly in while constructing the Private Linkage [1]. This kind of general platform checks should be migrated to OMR, although simply moving them to OMRGenerator leads to segmentation fault in JIT codegen. I am opening up this issue to keep track and document the reasons behind those failure. More details can be found in [2]
[1]. https://github.com/eclipse-openj9/openj9/blob/4ca209b54385134923881152273150eaf4847ac9/runtime/compiler/z/codegen/S390PrivateLinkage.cpp#L104-L113
[2]. #6558 (comment)
The text was updated successfully, but these errors were encountered: