[LLVMbugs] [Bug 77] New: Variables in scope of output setjmp calls should be volatile
bugzilla-daemon at zion.cs.uiuc.edu
bugzilla-daemon at zion.cs.uiuc.edu
Fri Oct 31 08:24:28 PST 2003
http://llvm.cs.uiuc.edu/bugs/show_bug.cgi?id=77
Summary: Variables in scope of output setjmp calls should be
volatile
Product: libraries
Version: trunk
Platform: All
OS/Version: All
Status: NEW
Severity: trivial
Priority: P2
Component: C backend
AssignedTo: sabre at nondot.org
ReportedBy: gaeke+bugs at uiuc.edu
ISO 9899 7.13.2.1 (3) says that "[...] the values of objects of automatic
storage duration that are local to the function containing the invocation of the
[...] setjmp macro that do not have volatile-qualified type and have been
changed between the setjmp invocation and longjmp call are indeterminate."
We should probably be marking all auto variables in the scope of a setjmp
volatile, to be safe. So far, this has not bitten us, but this seems to prove
only that we have been lucky.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
More information about the llvm-bugs
mailing list