This is an unofficial snapshot of the ISO/IEC JTC1 SC22 WG21 Core Issues List revision 119a. See http://www.open-std.org/jtc1/sc22/wg21/ for the official list.
2025-12-20
[Voted into WP at October, 2009 meeting.]
The execution requirements on a conforming implementation aredescribed twice in the Standard, once in 6.10.1 [intro.execution]paragraphs 5-6 and again in paragraph 11. These descriptions differin at least a couple of important ways:
The most significant discrepancy has to do with the way output isdescribed. In paragraph 11, the least requirements are described interms of data written at program termination, clearly allowingarbitrary buffering, whereas in paragraph 6, the observable behavioris described in terms of calls to I/O functions. For example, thereare compilers which transform a call to printf with a single argumentinto a call to fputs. That's valid under paragraph 11, but not underparagraph 6.
Also, in paragraph 6, volatile accesses and I/O operations areincluded in a single sequence, suggesting that they are equallyconstrained by sequencing requirements, whereas in paragraph 11, theyare clearly not.
There are also editorial discrepancies that should be cleanedup.
Proposed resolution (September, 2009):
The resolution ofissue 785 alsoresolves this issue.