https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63944
Joseph S. Myers changed:
What|Removed |Added
CC||ch3root at openwall dot com
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63944
Marek Polacek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63944
--- Comment #5 from Alexander Cherepanov ---
Not sure this is relevant to static/automatic distinction mentioned above but
the following code uses a static struct, is accepted by gcc and exposes the
problem:
-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63944
--- Comment #6 from joseph at codesourcery dot com ---
That's using the extension of allowing compound literals in static
initializers. Given that extension, we should fix such cases as well.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63944
Andrew Pinski changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
--- Comment #7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63944
--- Comment #1 from joseph at codesourcery dot com ---
Actually, I suppose the existing approach for strings could be used if
desired - split the struct into a series of component references to a
SAVE_EXPR of the nonconstant struct initializer
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63944
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
