On Tue, 13 Jan 2015, Jeff Law wrote: > In many ways having the compiler or assembler spitting out an error here is > preferable to silently compiling the code. That would also help explain why
As usual, an error is incorrect in such a case that only has undefined behavior at runtime (but it may be compiled into an abort if the behavior is unconditionally undefined, and the abort doesn't replace anything before the undefined behavior that might have stopped the undefined behavior from occurring). -- Joseph S. Myers jos...@codesourcery.com
