[Bug middle-end/91395] Report an uninitialized variable on its initialization statement (setjmp)

2019-08-08 Thread ali at pivotal dot io
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91395 --- Comment #4 from Adam --- (In reply to Andrew Pinski from comment #3) > In theory other can cause a call to longjmp but gcc does not know it cannot. Thanks for the quick reply. I got the longjmp() part, it could be called anytime. The part I

[Bug middle-end/91395] Report an uninitialized variable on its initialization statement (setjmp)

2019-08-08 Thread ali at pivotal dot io
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91395 --- Comment #2 from Adam --- I got the point "The local variables that do not have the volatile type and have been changed between the setjmp() invocation and longjmp() call are indeterminate" But save_exception_stack is not changed between the

[Bug c/91395] New: Report an uninitialized variable on its initialization statement (setjmp)

2019-08-07 Thread ali at pivotal dot io
: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: ali at pivotal dot io Target Milestone: --- Version: $ gcc-9 --version gcc-9 (Ubuntu 9.1.0-2ubuntu2~19.04) 9.1.0 (Actually from gcc 7) Reproducer: ``` #include extern int other