------- Comment #8 from 0xe2 dot 0x9a dot 0x9b at gmail dot com 2010-02-17
14:16 -------
(In reply to comment #7)
> Where the compiler always chooses some particular implementation is
> implementation defined behavior, not undefined behavior. Undefined behavior
> is
> always just that, undefined.
In comment #4 you wrote:
"There is nothing to fix. Your program triggers undefined behavior."
Why didn't you (as well as others here) write "triggers implementation defined
behavior"?
Doesn't that invalidate the first of your statements I cited here (namely:
"There is nothing to fix")?
ISO/IEC 9899:1999, section 6.3.1.3 states that the result is implementation
defined.
--
0xe2 dot 0x9a dot 0x9b at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43089
