diff options
| author | Roger Sayle <roger@nextmovesoftware.com> | 2021-09-17 15:57:34 +0100 |
|---|---|---|
| committer | Roger Sayle <roger@nextmovesoftware.com> | 2021-09-17 15:57:34 +0100 |
| commit | 2578a3870ef849dc77e98796600181b64ae4fd61 (patch) | |
| tree | 9f2347340d8588d96b01f059e809b7219f94156e /gcc/fortran/parse.c | |
| parent | 0a60524de103288347dd193937059e4e77c64079 (diff) | |
| download | gcc-2578a3870ef849dc77e98796600181b64ae4fd61.zip gcc-2578a3870ef849dc77e98796600181b64ae4fd61.tar.gz gcc-2578a3870ef849dc77e98796600181b64ae4fd61.tar.bz2 | |
PR c/102245: Disable sign-changing optimization for shifts by zero.
Respecting Jakub's suggestion that it may be better to warn-on-valid for
"if (x << 0)" as the author might have intended "if (x < 0)" [which will
also warn when x is _Bool], the simplest way to resolve this regression
is to disable the recently added fold transformation for shifts by zero;
these will be optimized later (elsewhere). Guarding against integer_zerop
is the simplest of three alternatives; the second being to only apply
this transformation to GIMPLE and not GENERIC, and the third (potentially)
being to explicitly handle shifts by zero here, with an (if cond then else),
optimizing the expression to a convert, but awkwardly duplicating a
more general transformation earlier in match.pd's shift simplifications.
2021-09-17 Roger Sayle <roger@nextmovesoftware.com>
gcc/ChangeLog
PR c/102245
* match.pd (shift optimizations): Disable recent sign-changing
optimization for shifts by zero, these will be folded later.
gcc/testsuite/ChangeLog
PR c/102245
* gcc.dg/Wint-in-bool-context-4.c: New test case.
Diffstat (limited to 'gcc/fortran/parse.c')
0 files changed, 0 insertions, 0 deletions