https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86714
Jeffrey A. Law changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86714
--- Comment #8 from Jeffrey A. Law ---
Author: law
Date: Wed Aug 29 17:17:08 2018
New Revision: 263963
URL: https://gcc.gnu.org/viewcvs?rev=263963&root=gcc&view=rev
Log:
PR tree-optimization/86714
PR tree-optimization/86711
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86714
Martin Sebor changed:
What|Removed |Added
Keywords||patch
--- Comment #7 from Martin Sebor -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86714
Martin Sebor changed:
What|Removed |Added
Status|REOPENED|ASSIGNED
Assignee|unassigned at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86714
--- Comment #5 from Martin Sebor ---
I didn't overlook anything. I replied and explained what happens here:
https://gcc.gnu.org/ml/gcc-patches/2018-07/msg01272.html
Since the undefined behavior in this case is at compile time, rejecting the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86714
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86714
Richard Biener changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86714
--- Comment #2 from Bernd Edlinger ---
You must have overlooked this response from Jakub:
https://gcc.gnu.org/ml/gcc-patches/2018-07/msg01238.html
"If we just warn about the initializer and treat it some way, an optimization
should not change h
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86714
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
