https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99797
Martin Uecker changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
Resolution|INVALID
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99797
--- Comment #6 from Martin Uecker ---
Annex J is not normative. The normative text is the one I cited and that
mentions "address taken". Reading an indeterminate values is not UB if it is
not a trap representation and then yield an unspecified
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99797
--- Comment #5 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #4)
> (In reply to Martin Uecker from comment #3)
> > The C standard says (6.3.2.1p2)
>
> J.2 Undefined behavior
>
> — The value of an object with automatic storage d
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99797
--- Comment #4 from Andrew Pinski ---
(In reply to Martin Uecker from comment #3)
> The C standard says (6.3.2.1p2)
J.2 Undefined behavior
— The value of an object with automatic storage duration is used while it is
indeterminate (6.2.4, 6.7.9,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99797
--- Comment #3 from Martin Uecker ---
The C standard says (6.3.2.1p2)
"... If the lvalue designates an object of automatic storage duration
that could have been declared with the register storage class
(never had its address taken), and that ob
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99797
Andrew Pinski changed:
What|Removed |Added
Resolution|WONTFIX |INVALID
--- Comment #2 from Andrew Pinsk
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99797
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |WONTFIX
Status|UNCONFIRMED
