[Bug middle-end/110726] [14 Regression] wrong code on llvm-16 around 'a |= a == 0'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110726 Andrew Pinski changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug middle-end/110726] [14 Regression] wrong code on llvm-16 around 'a |= a == 0'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110726 --- Comment #11 from CVS Commits --- The trunk branch has been updated by Andrew Pinski : https://gcc.gnu.org/g:bf20b770d9aabb15faf2644b5e3106249cb175f3 commit r14-2648-gbf20b770d9aabb15faf2644b5e3106249cb175f3 Author: Andrew Pinski Date:

[Bug middle-end/110726] [14 Regression] wrong code on llvm-16 around 'a |= a == 0'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110726 --- Comment #10 from Sergei Trofimovich --- (In reply to Andrew Pinski from comment #5) > Created attachment 55575 [details] > Patch which should fix this This fixed llvm-16 test suite for me. Thank you!

[Bug middle-end/110726] [14 Regression] wrong code on llvm-16 around 'a |= a == 0'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110726 Andrew Pinski changed: What|Removed |Added Keywords||patch URL|

[Bug middle-end/110726] [14 Regression] wrong code on llvm-16 around 'a |= a == 0'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110726 --- Comment #8 from Andrew Pinski --- (In reply to Sergei Trofimovich from comment #7) > Silly question: I would expect -O0 not to perform any simplifications like > that. Does `gcc` have a knob to disable `match.pd` templates? Or some of >

[Bug middle-end/110726] [14 Regression] wrong code on llvm-16 around 'a |= a == 0'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110726 --- Comment #7 from Sergei Trofimovich --- Silly question: I would expect -O0 not to perform any simplifications like that. Does `gcc` have a knob to disable `match.pd` templates? Or some of them are crucial for correctness?

[Bug middle-end/110726] [14 Regression] wrong code on llvm-16 around 'a |= a == 0'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110726 --- Comment #6 from Andrew Pinski --- Created attachment 55576 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55576=edit Full testcase

[Bug middle-end/110726] [14 Regression] wrong code on llvm-16 around 'a |= a == 0'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110726 --- Comment #5 from Andrew Pinski --- Created attachment 55575 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55575=edit Patch which should fix this So I didn't realize I need the check for "INTEGRAL_TYPE_P (TREE_TYPE (@0)) &&

[Bug middle-end/110726] [14 Regression] wrong code on llvm-16 around 'a |= a == 0'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110726 --- Comment #4 from Andrew Pinski --- /* a | (a == b) --> a | (b^1) (boolean version of the above). */ (simplify (bit_ior:c @0 (nop_convert? (eq:c @0 @1))) (bit_ior @0 (bit_xor @1 { build_one_cst (type); }))) So I guess the issue is eq on

[Bug middle-end/110726] [14 Regression] wrong code on llvm-16 around 'a |= a == 0'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110726 Andrew Pinski changed: What|Removed |Added Status|NEW |ASSIGNED

[Bug middle-end/110726] [14 Regression] wrong code on llvm-16 around 'a |= a == 0'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110726 Andrew Pinski changed: What|Removed |Added Last reconfirmed||2023-07-18

[Bug middle-end/110726] [14 Regression] wrong code on llvm-16 around 'a |= a == 0'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110726 Andrew Pinski changed: What|Removed |Added Keywords||wrong-code Target Milestone|---

[Bug middle-end/110726] [14 Regression] wrong code on llvm-16 around 'a |= a == 0'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110726 --- Comment #2 from Andrew Pinski --- Whoops wrong bug report.

[Bug middle-end/110726] [14 Regression] wrong code on llvm-16 around 'a |= a == 0'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110726 --- Comment #1 from Andrew Pinski --- I think this will be fixed with -momit-leaf-frame-pointer patch at : https://gcc.gnu.org/pipermail/gcc-patches/2023-July/624752.html