[Bug tree-optimization/88916] [x86] suboptimal code generated for integer comparisons joined with boolean operators

2022-11-26 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88916 Andrew Pinski changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

[Bug tree-optimization/88916] [x86] suboptimal code generated for integer comparisons joined with boolean operators

2022-11-26 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88916 Andrew Pinski changed: What|Removed |Added Known to work||13.0 --- Comment #4 from Andrew Pinski

[Bug tree-optimization/88916] [x86] suboptimal code generated for integer comparisons joined with boolean operators

2021-08-10 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88916 Andrew Pinski changed: What|Removed |Added CC||pinskia at gcc dot gnu.org Sev

[Bug tree-optimization/88916] [x86] suboptimal code generated for integer comparisons joined with boolean operators

2019-01-22 Thread wojciech_mula at poczta dot onet.pl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88916 --- Comment #3 from Wojciech Mula --- A similar case: ---sign.c--- int different_sign(long a, long b) { return (a >= 0 && b < 0) || (a < 0 && b >= 0); } ---eof-- This is compiled into: different_sign: notq%rdi movq%

[Bug tree-optimization/88916] [x86] suboptimal code generated for integer comparisons joined with boolean operators

2019-01-21 Thread wojciech_mula at poczta dot onet.pl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88916 --- Comment #2 from Wojciech Mula --- (In reply to Richard Biener from comment #1) > Confirmed. The first case is OK, but the second (for `both_nonzero`) is obviously wrong. Sorry for that.

[Bug tree-optimization/88916] [x86] suboptimal code generated for integer comparisons joined with boolean operators

2019-01-21 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88916 Richard Biener changed: What|Removed |Added Target||x86_64-*-*, i?86-*-* Status