[Bug c/96468] Warn when an empty while loop could have been a do-while

2020-08-06 Thread egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96468 Eric Gallager changed: What|Removed |Added CC||egallager at gcc dot gnu.org --- Comment

[Bug c/96468] Warn when an empty while loop could have been a do-while

2020-08-05 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96468 Martin Sebor changed: What|Removed |Added Component|tree-optimization |c --- Comment #6 from Martin Sebor --- O

[Bug c/96468] Warn when an empty while loop could have been a do-while

2020-08-05 Thread josephcsible at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96468 --- Comment #3 from Joseph C. Sible --- I didn't intend to restrict this to only volatile control variables. If you have "_Bool canMoveOn(void);", I'd like "while(!canMoveOn());" in place of "while(!signaled);" to warn too for the exact same reas

[Bug c/96468] Warn when an empty while loop could have been a do-while

2020-08-05 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96468 Martin Sebor changed: What|Removed |Added CC||msebor at gcc dot gnu.org --- Comment #2

[Bug c/96468] Warn when an empty while loop could have been a do-while

2020-08-05 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96468 Richard Biener changed: What|Removed |Added Severity|normal |enhancement Ever confirmed|0