Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tril tests are not able to detect the right CPU level on Z #7204

Open
dchopra001 opened this issue Dec 13, 2023 · 0 comments
Open

tril tests are not able to detect the right CPU level on Z #7204

dchopra001 opened this issue Dec 13, 2023 · 0 comments

Comments

@dchopra001
Copy link
Contributor

Removing a SKIP_ON_S390 check like the one below:
https://github.com/eclipse/omr/blob/149b5245ac056f5025d141760ea995822fc30c74/fvtest/compilertriltest/VectorTest.cpp#L313-L322

Results in Assertion failures on Z:

Assertion failed at /home/dchopra/openj9-openjdk-jdk17/omr/compiler/z/codegen/OMRInstruction.cpp:89:() cg->comp()->target().cpu.isAtLeast(_opcode.getMinimumALS())
	Processor detected (Unknown) does not support instruction VL

It looks like the processor is not detected properly. This is most likely happening because we call the default constructor for OMRCPU here:
https://github.com/eclipse/omr/blob/0d4b2da9e86466d10e8f9a77cc3521c4b9548341/compiler/z/env/OMRCPU.cpp#L34-L42

The call to detect is made here:
https://github.com/eclipse/omr/blob/149b5245ac056f5025d141760ea995822fc30c74/fvtest/compilertriltest/VectorTest.cpp#L327-L331

Is privateOmrPortLibrary expected to be null here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant