Loop optimizer issues

Steven Bosscher s.bosscher@student.tudelft.nl
Thu Jul 3 18:45:00 GMT 2003


Op do 03-07-2003, om 20:12 schreef Zdenek Dvorak:
> > Btw. I would agree that most of those constructs resulting in libcalls
> > should already have been optimized by tree-ssa, but OTOH I have
> > difficulties understanding why removing supporting libcalls would be so
> > much easier to implement.  libcalls for REG_NO_CONFLICT blocks are simply
> > funny multi-pattern statements, and libcalls with just calls, are well,
> > simply calls.  Why is it so much easier to not handle them?
> 
> It is not somehow terribly difficult (a hundred or two of lines of code,
> I guess); but IMO it would be nice to get rid of this feature with
> tree-ssa completely.

But (and here we go again...) not all front ends use tree-ssa, so while
tree-ssa gets rid of it for the front ends that use it, the others
(read: g77, Ada (Kenner! ;-)) are stuck with a crippled optimizer.  That
may or may not be a reason to keep this particular code around, I don't
care.  But let's not just pronounce parts or RTL passes just redundant
until all front ends use tree-ssa.

Gr.
Steven



More information about the Gcc mailing list