https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108117
--- Comment #6 from Feng Xue <fxue at os dot amperecomputing.com> --- (In reply to Andrew Pinski from comment #2) > https://en.cppreference.com/w/c/program/setjmp I think that most programmers are not aware of this, neither I for sure. Usage of volatile here is not that intuitive as for purpose of multi-execution synchronization, it just tells compiler to keep variable in memory, instead of register. With current SSA representation in GCC, probably, this could be automatically identified without explicit source level specifier. That is, any SSA name occurring in abnormal phi should go to memory during expansion to rtl.
