------- Comment #9 from edmar at freescale dot com 2010-06-21 23:36 ------- Hummm, I will work on your input, But now I have more questions:
1) Why do you call this case as explicit, and function call arguments implicit ? The way I see it, this is a special function call (implemented with a jump_insn to save space). So, why r11 is not a function call argument ? 2) On other targets, and indirect calls, gcc generates a parallel but still uses a call_insn to represent it. Which causes build_def_use() to avoid register renaming of these arguments. So other targets would not be slowed down, because those cases have to be avoided. 3) On the other hand, can you give me an example of a jump_insn, with a parallel, and a symbol reference, where a register rename would be valid ? Wouldn't all those registers be considered function call arguments ? (Perhaps I should add a test for the existence of a symbol reference in my patch. If the symbol reference is external or global, registers can never be renamed !) Thanks, Edmar -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44618
