[Bug tree-optimization/21712] missed optimization due with const function and pulling out of loops

rakdver at atrey dot karlin dot mff dot cuni dot cz gcc-bugzilla@gcc.gnu.org
Sun May 22 21:13:00 GMT 2005


------- Additional Comments From rakdver at atrey dot karlin dot mff dot cuni dot cz  2005-05-22 21:13 -------
Subject: Re:  missed optimization due with const function and pulling out of loops

> > Nevertheless, even if we are very strict with the definition, moving
> > get_type2 out of the loop is not a good idea, since get_type2 might
> > potentially be very expensive (and we have no way how to determine
> > that this is not the case), thus we would lose in case get_type2
> > should be never executed.
> > 
> > 
> 
> Don't we attempt to detect zero trip loops?
> (If not, we should :P)

I don't see how this is relevant to the PR.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21712



More information about the Gcc-bugs mailing list