https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65455
--- Comment #14 from Jens Gustedt <jens.gustedt at inria dot fr> --- Perhaps we should end the discussion here, this goes too far for a bug report, and we should push for a solution of this type of questions by the C committee. Perhaps you could leave this "bug" open, even if you don't agree that it is a bug in gcc itself. It certainly is an "issue" that users of that feature in gcc should be aware of. I think that this should be resolved in one way or another, best by having a clear policy in the C standard itself what to do in such situations.