[Bug middle-end/19430] taking address of a var causes missing uninitialized warning (virtual PHI with MEM)

2021-03-31 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19430 Martin Sebor changed: What|Removed |Added CC||scott.d.phillips at intel dot com --- Co

[Bug middle-end/19430] taking address of a var causes missing uninitialized warning (virtual PHI with MEM)

2020-10-27 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19430 Martin Sebor changed: What|Removed |Added CC||msebor at gcc dot gnu.org --- Comment

Bug#33975: [Bug c++/6905] Suggested g++ warning: changed semantics of conditional expressions

2017-02-27 Thread msebor at gcc dot gnu.org
||msebor at gcc dot gnu.org Resolution|--- |WONTFIX --- Comment #2 from Martin Sebor --- Resolving as Won't Fix due to no progress in 14+ years. The standard rules are now well established and so the usefulness of such a warning diminishes with

[Bug target/28314] cpp: x86/powerpc inconsistency for the __linux macro

2016-01-25 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28314 --- Comment #6 from Martin Sebor --- I opened bug 69473 to document the macros. -- You are receiving this mail because: You reported the bug.

[Bug target/28314] cpp: x86/powerpc inconsistency for the __linux macro

2016-01-25 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28314 --- Comment #5 from Martin Sebor --- FWIW, while looking into this bug I couldn't find the topic discussed in the LSB where I would expect this to be specified. I did come across a couple of sites on the web that gather this type of information.

[Bug target/28314] cpp: x86/powerpc inconsistency for the __linux macro

2016-01-24 Thread msebor at gcc dot gnu.org
||msebor at gcc dot gnu.org Known to fail||4.1.2, 4.5.3, 4.8.3, 4.9.3, ||5.3.0, 6.0 --- Comment #2 from Martin Sebor --- This hasn't changed in 10 years. Should the bug be closed as WONTFIX? --