This is the mail archive of the
mailing list for the GCC project.
Re: [tree-ssa] Virtual operands in tree-tailcall
> >while playing with new loop invariant motion pass,
> Just to note, you need to be careful with invariant motion. It's not
> always good to hoist everything we can (as it can increase register
> It's almost always good to move invariant memory loads/sink invariant
> memory stores, though.
> I'm just talking about general loop invariants.
yes, I am aware of this. In fact I would like to move only the
"obviously beneficial" invariants on tree level (so that we may get
rid of libcall notes), and leave the rest on rtl level pass that may
much better estimate things like costs of the computations and register