Re: [PATCH] i386: Separate costs of RTL expressions from costs of moves

2019-06-24 Thread H.J. Lu
On Mon, Jun 24, 2019 at 6:37 AM Richard Biener wrote: > > On Thu, 20 Jun 2019, Jan Hubicka wrote: > > > > > Currently, costs of moves are also used for costs of RTL expressions. > > > > This > > > > patch: > > > > > > > > https://gcc.gnu.org/ml/gcc-patches/2018-02/msg00405.html > > > > > > > >

Re: [PATCH] i386: Separate costs of RTL expressions from costs of moves

2019-06-24 Thread Richard Biener
On Thu, 20 Jun 2019, Jan Hubicka wrote: > > > Currently, costs of moves are also used for costs of RTL expressions. > > > This > > > patch: > > > > > > https://gcc.gnu.org/ml/gcc-patches/2018-02/msg00405.html > > > > > > includes: > > > > > > diff --git a/gcc/config/i386/x86-tune-costs.h > > >

Re: [PATCH] i386: Separate costs of RTL expressions from costs of moves

2019-06-23 Thread Jan Hubicka
> I opened: > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90952 > > We shouldn't use costs for moves for costs of RTL expressions. We can > experiment different RTL expression cost formulas. But we need to separate > costs of RTL expressions from costs for moves first. What is the best w

Re: [PATCH] i386: Separate costs of RTL expressions from costs of moves

2019-06-20 Thread H.J. Lu
On Thu, Jun 20, 2019 at 2:10 PM Jan Hubicka wrote: > > > > Currently, costs of moves are also used for costs of RTL expressions. > > > This > > > patch: > > > > > > https://gcc.gnu.org/ml/gcc-patches/2018-02/msg00405.html > > > > > > includes: > > > > > > diff --git a/gcc/config/i386/x86-tune-c

Re: [PATCH] i386: Separate costs of RTL expressions from costs of moves

2019-06-20 Thread Jan Hubicka
> > Currently, costs of moves are also used for costs of RTL expressions. This > > patch: > > > > https://gcc.gnu.org/ml/gcc-patches/2018-02/msg00405.html > > > > includes: > > > > diff --git a/gcc/config/i386/x86-tune-costs.h > > b/gcc/config/i386/x86-tune-costs.h > > index e943d13..8409a5f 100

Re: [PATCH] i386: Separate costs of RTL expressions from costs of moves

2019-06-20 Thread Uros Bizjak
On Thu, Jun 20, 2019 at 5:19 PM H.J. Lu wrote: > > On Thu, Jun 20, 2019 at 12:43 AM Uros Bizjak wrote: > > > > On Thu, Jun 20, 2019 at 9:40 AM Uros Bizjak wrote: > > > > > > On Mon, Jun 17, 2019 at 6:27 PM H.J. Lu wrote: > > > > > > > > processor_costs has costs of RTL expressions and costs of

Re: [PATCH] i386: Separate costs of RTL expressions from costs of moves

2019-06-20 Thread H.J. Lu
On Thu, Jun 20, 2019 at 12:43 AM Uros Bizjak wrote: > > On Thu, Jun 20, 2019 at 9:40 AM Uros Bizjak wrote: > > > > On Mon, Jun 17, 2019 at 6:27 PM H.J. Lu wrote: > > > > > > processor_costs has costs of RTL expressions and costs of moves: > > > > > > 1. Costs of RTL expressions is computed as CO

Re: [PATCH] i386: Separate costs of RTL expressions from costs of moves

2019-06-20 Thread Uros Bizjak
On Thu, Jun 20, 2019 at 9:40 AM Uros Bizjak wrote: > > On Mon, Jun 17, 2019 at 6:27 PM H.J. Lu wrote: > > > > processor_costs has costs of RTL expressions and costs of moves: > > > > 1. Costs of RTL expressions is computed as COSTS_N_INSNS which are used > > to generate RTL expressions with the l

Re: [PATCH] i386: Separate costs of RTL expressions from costs of moves

2019-06-20 Thread Uros Bizjak
On Mon, Jun 17, 2019 at 6:27 PM H.J. Lu wrote: > > processor_costs has costs of RTL expressions and costs of moves: > > 1. Costs of RTL expressions is computed as COSTS_N_INSNS which are used > to generate RTL expressions with the lowest costs. Costs of RTL memory > operation can be very close to

[PATCH] i386: Separate costs of RTL expressions from costs of moves

2019-06-17 Thread H.J. Lu
uot; Date: Fri, 14 Jun 2019 13:30:16 -0700 Subject: [PATCH] i386: Separate costs of RTL expressions from costs of moves processor_costs has costs of RTL expressions and costs of moves: 1. Costs of RTL expressions is computed as COSTS_N_INSNS which are used to generate RTL expressions with the lowest co