https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96810
--- Comment #5 from Wei Wentao ---
Sorry for the last comment.I don't know how this happened.
Let's get to the point.
>>And while the bug described in the comment is really hard to diagnose at
>>compile time and in most cases impossible, what
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96810
--- Comment #4 from Wei Wentao ---
>>--- Comment #3 from Jakub Jelinek ---
>>Actually sorry, the diagnostics clang emits is not about the bug mentioned in
>>the testcase, but about something different.
>>And while the bug described in the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96810
--- Comment #2 from Wei Wentao ---
> --- Comment #1 from Jakub Jelinek ---
> >The standard says this is unspecified behavior, but the unspecified behavior
> >happens at runtime, so if the compiler could detect it at compile time, it
> >would
: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: weiwt.fnst at cn dot fujitsu.com
Target Milestone: ---
In the examples below, gcc has opposite behavior when complie:
These examples are from:
https://www.openmp.org/wp
