On Fri, Oct 14, 2011 at 19:19, Georg-Johann Lay <a...@gjlay.de> wrote: > Paolo Bonzini schrieb: >> On 10/14/2011 06:23 PM, Georg-Johann Lay wrote: >>> +@item -mjump-to-noreturn >>> +@opindex mjump-to-noreturn >>> +Use a jump instruction instead of a call instruction when calling a >>> +no-return functions. This option is active if optimization is turned >>> +on and just affects the way a call instruction is printed out. >>> +Besides that, it has no effect on code generation or debug information. >> >> I think this is not really accurate given Richard's input. > > Confused. The conclusion was to introduce a new command line option in order > to have individual control over this feature. The option is named > -mjump-to-noreturn now instead of -mjump-noreturn. Is that what you mean?
No, I mean that it has an effect on debuggability. You will not be able to derive the place where you crashed from the backtrace. Paolo
