------- Comment #10 from ebotcazou at gcc dot gnu dot org 2009-07-06 15:31 ------- > Well, why? For save or called saved registers the functions epilogue/prologue > takes care. The reason why gcc tries to choose ebx for call address register > here, is exactly this reason, as it can be sure that after the sibcall, the > register is still valid.
What's the assembly code generated with your patch? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38900
