On 4/17/07, Kenneth Hoste <[EMAIL PROTECTED]> wrote:
* On x86, -fschedule-insns is disabled, but -fschedule-insns2 (or the corresponding internal flag flag_schedule_insns_after_reload) is still being used... The reason for disabling fschedule-insns is increased register pressure (and x86 has few registers already). I'm not sure if this a bug, but why disable -fschedule-insns and leave - fschedule-insns2 active? Because , according to the docs, fschedule- insns2 = fschedule-insns + an additional pass. Any comments on this are welcome...
-fschedule-insns2 is scheduling after register allocation. Register pressure is not a problem after register allocation ;-) You just have more constraints in your scheduling dependency graph. Gr. Steven
