Skip to content

Comments

[Backport staging-22.11] gcc: Backport fix of GCC Issue 80431 from version 12#211255

Merged
Ericson2314 merged 1 commit intostaging-22.11from
backport-210816-to-staging-22.11
Jan 17, 2023
Merged

[Backport staging-22.11] gcc: Backport fix of GCC Issue 80431 from version 12#211255
Ericson2314 merged 1 commit intostaging-22.11from
backport-210816-to-staging-22.11

Conversation

@github-actions
Copy link
Contributor

Bot-based backport to staging-22.11, triggered by a label in #210816.

  • Before merging, ensure that this backport complies with the Criteria for Backporting.
    • Even as a non-commiter, if you find that it does not comply, leave a comment.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80431

This bug annoys me because I hit it when working on Nix. It causes
miscompilations in such a way that I am hard-pressed to think how a
program could inadvertainly rely on the bug (such that it would be
broken by the fix).

The bug is longstanding, and the (quite small) applies without
modification to many older GCCs. I have confirmed by running the test in
that commit that does indeed fix the bug with the backports too.

(cherry picked from commit d6d1897)
@Ericson2314
Copy link
Member

Not sure what ofborg is doing, but I hand-double-checked eval.

@Ericson2314 Ericson2314 merged commit 67d37da into staging-22.11 Jan 17, 2023
@Ericson2314 Ericson2314 deleted the backport-210816-to-staging-22.11 branch January 17, 2023 16:59
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

Successfully merging this pull request may close these issues.

1 participant