[Bug tree-optimization/35805] [ira] error in start_allocno_priorities, at ira-color.c:1806

Paolo Bonzini bonzini@gnu.org
Fri Jan 2 14:26:00 GMT 2009

> I think so.   The global changed flag allows it to delete the case:
> loop:
>  ... <- x  // This is dead.
>  x- <- ...
> go to loop
> it just is not going to get rid of it if there is is no kill of x inside
> the loop.

I just don't think it's acceptable to load each and every "fast DCE"
with the burden of a full df solution.  We need to find a way to limit
this to the cases when it is needed, or at least not to be too
conservative in ascertaining *when* it is needed.

Hence my first and foremost question is: does it happen that the
solution is wrong and global_changed never became true?

If the answer is "definitely no", then an alternative preferrable
patch would be to move the code you added to df-problems.c into dce.c,
so that the full analysis (including rebuilding the bitmaps and
iterating possibly many times) is not run if it was to yield the same
answer that was before in the bitmaps.


More information about the Gcc-patches mailing list