On Fri, May 01, 2020 at 07:21:31PM +0200, Arnd Bergmann wrote: > On Thu, Apr 30, 2020 at 4:05 PM Arnd Bergmann <a...@arndb.de> wrote: > it gets into undefined behavior and stops emitting code after the call to
> Do we consider this expected behavior on gcc's side, or is it something > that should not happen and needs a gcc bug report? When it hits UB it is of course free to do whatever it damn well pleases, but just stopping code gen seems a little extreme, at least issue a WARN that something is up or so. Not sure how the GCC folks feel about this though.