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

LLVM's maxnum builder is broken in LLVM6 #49261

Closed
gnzlbg opened this issue Mar 22, 2018 · 4 comments
Closed

LLVM's maxnum builder is broken in LLVM6 #49261

gnzlbg opened this issue Mar 22, 2018 · 4 comments
Labels
A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug.

Comments

@gnzlbg
Copy link
Contributor

gnzlbg commented Mar 22, 2018

This was fixed in this LLVM commit: llvm-mirror/llvm@e271f8c

Once we upgrade to LLVM 7 a couple of fail tests are going to start passing because of this.

This issue is referenced in all parts of the code that need updating.

@sanxiyn sanxiyn added the A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. label Mar 28, 2018
@cuviper
Copy link
Member

cuviper commented Apr 26, 2018

When testing with LLVM master, I just hit a test "failure" on run-fail/simd-intrinsic-float-minmax.rs, because the run actually passed! IMO this is the wrong use of run-fail -- these should be tests that are supposed to fail, not just "known to fail because of a bug."

Wouldn't it be better to make that test a run-pass, marked with min-llvm-version 7.0? Or maybe run-pass with the known-broken parts FIXME-commented out?

@gnzlbg
Copy link
Contributor Author

gnzlbg commented Apr 27, 2018

@cuviper that makes sense.

Wouldn't it be better to make that test a run-pass, marked with min-llvm-version 7.0?

Now that we know the test passes with master, then yes. But I did not test it with master, so I did not know. I wanted that to be loud the first time somebody did that so that we can move the test to run-pass. I did not thought about somebody testing with master though, I thought this would just happen when we tried to upgrade to LLVM7. Sorry about that.

Now that we know the fix in master really did fix this, moving it to run-pass with min-llvm-version 7.0 makes sense.

@kennytm kennytm added the C-bug Category: This is a bug. label Apr 27, 2018
@gnzlbg
Copy link
Contributor Author

gnzlbg commented May 4, 2018

@cuviper I'll fix that this weekend if somebody doesn't beat me to it.

@gnzlbg
Copy link
Contributor Author

gnzlbg commented Jun 4, 2018

Closed in #50521

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug.
Projects
None yet
Development

No branches or pull requests

4 participants