https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86714
--- Comment #5 from Martin Sebor <msebor at gcc dot gnu.org> --- 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 code should be a valid/conforming response. IMO, either issuing an error or truncating it would be preferable to trying to deal with it in the middle-end. I think we've already agreed on the latter approach in the discussion of another bug. Rejecting it would be even better.
