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

refuse to build when Cray compiler is detected for CPU-only builds #566

Open
BenWibking opened this issue Mar 17, 2024 · 2 comments
Open
Labels
compiler bug caused by a bug in a compiler, not in the code itself enhancement New feature or request

Comments

@BenWibking
Copy link
Collaborator

BenWibking commented Mar 17, 2024

Describe the proposal
We refuse to build when the Cray C/C++ Compiler (cce) is detected and we are doing a CPU-only build. It miscompiles the code and produces wrong output.

However, when doing a GPU build, it works fine.

Additional context
@chongchonghe found that compiling using cce/15.0.1 causes the test suite to fail on CPU, but works on GPU.

@BenWibking BenWibking added enhancement New feature or request compiler bug caused by a bug in a compiler, not in the code itself labels Mar 17, 2024
@psharda
Copy link
Contributor

psharda commented Mar 18, 2024

So this is an issue if you compile using setonix-cpu.profile and setonix-gpu.profile?

@BenWibking
Copy link
Collaborator Author

So this is an issue if you compile using setonix-cpu.profile and setonix-gpu.profile?

Yes.

@psharda psharda mentioned this issue Mar 18, 2024
7 tasks
@BenWibking BenWibking changed the title set -fno-cray when Cray compiler is detected refuse to build when Cray compiler is detected for CPU-only builds Mar 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
compiler bug caused by a bug in a compiler, not in the code itself enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants