This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Fix code quality regression on UltraSPARC


> Agreed.  In fact, with your proposed fallthruness test of the latch
> edge, I don't think we need to be much cleverer than we were before.

I actually was under the same impression.

> Can you check whether the following subset of your patch is sufficient
> to improve the UltraSPARC code we generate for gzip?

Yes, the fallthruness test of the latch edge is enough in this case (verified 
on t28.ch and the final assembly code).

> I'm just trying to figure out which of your changes are necessary
> and which are sufficient.  The "one_succ_pred" is a nice refinement,
> but I no longer think the FOR_EACH_EDGE/best_pred->next_bb helps
> any.

Agreed.

> This also finesses your question "??? Can this ever happen?", 
> to which the answer is yes it can.

Do you mean the latch is allowed to have more than one edge to the header?

-- 
Eric Botcazou


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]