-
Notifications
You must be signed in to change notification settings - Fork 772
add patch to fix miscompilation bug on POWER for GCC 8.x and 9.x #11837
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
add patch to fix miscompilation bug on POWER for GCC 8.x and 9.x #11837
Conversation
|
Test report by @Flamefire |
|
Test report by @Flamefire |
Micket
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
|
@boegelbot please test @ generoso |
|
@Micket: Request for testing this PR well received on generoso PR test command '
Test results coming soon (I hope)... Details- notification for comment with ID 740027004 processed Message to humans: this is just bookkeeping information for me, |
|
Test report by @boegelbot |
|
@Micket The log doesn't contain the information about what went wrong with GCC 8.1. I'd assume a flake somewhere but can't tell. This should not make it fail where it worked before. |
|
Test report by @Micket |
|
(edit: ignore this failure, I probably messed it up) |
|
Test report by @Micket |
|
Test report by @Micket |
|
The GCC 8.1 failure is: The glibc 2.28 release notes say:
So, the failure on CentOS 8 is not caused by the changes in this PR. |
|
Test report by @branfosj |
|
The CentOS failure is aweful, but the patch should be pretty easy: There is See commit 71b55d45e4304f5e2e98ac30473c581f58fc486b from the github GCC mirror |
|
Going in, thanks @Flamefire! |
|
making sure boegelbot has the patched versions built for its the toolchains so that it we can properly test it out with the rest of the PRs: |
|
@Micket: Request for testing this PR well received on generoso PR test command '
Test results coming soon (I hope)... Details- notification for comment with ID 746764885 processed Message to humans: this is just bookkeeping information for me, |
|
I expect 8.1.0 to fail here, but if anyone cares about it, then lets make a new PR for that fix. |
|
@boegelbot please test @ generoso (@Micket I cancelled the previous job, was only using 4 cores...) |
|
@boegel: Request for testing this PR well received on generoso PR test command '
Test results coming soon (I hope)... Details- notification for comment with ID 746928428 processed Message to humans: this is just bookkeeping information for me, |
|
Test report by @boegelbot |
|
@boegel Lock file on 8.3.0 build present |
|
@boegelbot please test @ generoso (lock file for GCC 8.3.0 removed) |
|
@boegel: Request for testing this PR well received on generoso PR test command '
Test results coming soon (I hope)... Details- notification for comment with ID 747919475 processed Message to humans: this is just bookkeeping information for me, |
|
Hmm, that |
|
Found your bug: See |
|
Should be just one max split |
|
Ouch... Thanks, that was so easy to overlook. |
|
@boegelbot please test @ generoso |
|
@boegel: Request for testing this PR well received on generoso PR test command '
Test results coming soon (I hope)... Details- notification for comment with ID 748020112 processed Message to humans: this is just bookkeeping information for me, |
|
Test report by @boegelbot |
(created using
eb --new-pr)This fixes a bug when using GCC to compile code of the form
(x > b) ? b : xon POWER which leads to GCC emitting a hardware instruction which does not correctly handle the NaN and signed zero cases, i.e. it would wrongly yieldbwhen x isnan