Re: Do not combine PRED_LOOP_GUARD and PRED_LOOP_GUARD_WITH_RECURSION

2020-08-13 Thread Martin Liška
On 8/12/20 1:02 PM, Tamar Christina wrote: Hmm the regression on exchange2 is 11%. Or 1.22% on specint 2017 overall.. This is a rather big regression.. What would be the correct way to do this? I can confirm that many our LNT tester configurations spotted that: https://lnt.opensuse.org/db_defa

RE: Do not combine PRED_LOOP_GUARD and PRED_LOOP_GUARD_WITH_RECURSION

2020-08-12 Thread Tamar Christina
Hi Honza, > -Original Message- > From: Gcc-patches On Behalf Of Jan > Hubicka > Sent: Tuesday, August 11, 2020 11:04 AM > To: gcc-patches@gcc.gnu.org > Subject: Do not combine PRED_LOOP_GUARD and > PRED_LOOP_GUARD_WITH_RECURSION > > Hi, > this patch a

Do not combine PRED_LOOP_GUARD and PRED_LOOP_GUARD_WITH_RECURSION

2020-08-11 Thread Jan Hubicka
Hi, this patch avoids both PRED_LOOP_GUARD and PRED_LOOP_GUARD_WITH_RECURSION to be attached to one edge. We have logic that prevents same predictor to apply to one edge twice, but since we split LOOP_GUARD to two more specialized cases, this no longer fires. Double prediction happens in exchange