Re: [PATCH, PR target/65103, 1/3] Fix cost of PIC register in ix86_address_cost

2015-03-12 Thread Uros Bizjak
On Thu, Mar 12, 2015 at 10:50 AM, Ilya Enkovich wrote: >> > > > Test O2 ref patchedOfast + LTO ref patched >> > > > 164.gzip12 0 (-100%)39 0 (-100%) >> > > > 175.vpr 0 0 (-0%) 4 0 (-100%) >> > > > 176.gcc 141

Re: [PATCH, PR target/65103, 1/3] Fix cost of PIC register in ix86_address_cost

2015-03-12 Thread Ilya Enkovich
On 10 Mar 19:08, Uros Bizjak wrote: > Hello! > > > > > Test O2 ref patchedOfast + LTO ref patched > > > > 164.gzip12 0 (-100%)39 0 (-100%) > > > > 175.vpr 0 0 (-0%) 4 0 (-100%) > > > > 176.gcc 141 6 (-96%)

Re: [PATCH, PR target/65103, 1/3] Fix cost of PIC register in ix86_address_cost

2015-03-12 Thread Uros Bizjak
Hello! > > > Test O2 ref patchedOfast + LTO ref patched > > > 164.gzip12 0 (-100%)39 0 (-100%) > > > 175.vpr 0 0 (-0%) 4 0 (-100%) > > > 176.gcc 141 6 (-96%) 294 10 (-97%) > > > 181.mcf

Re: [PATCH, PR target/65103, 1/3] Fix cost of PIC register in ix86_address_cost

2015-03-10 Thread Ilya Enkovich
On 10 Mar 16:17, Jakub Jelinek wrote: > On Tue, Mar 10, 2015 at 05:54:46PM +0300, Ilya Enkovich wrote: > > This patches set addresses the problem of inefficient usage of x86 > > addressing modes in PIC. Looking into generated 32bit PIC assembler we may > > see lots of 'leal @GOTOFF, %reg' instr

Re: [PATCH, PR target/65103, 1/3] Fix cost of PIC register in ix86_address_cost

2015-03-10 Thread Jakub Jelinek
On Tue, Mar 10, 2015 at 05:54:46PM +0300, Ilya Enkovich wrote: > This patches set addresses the problem of inefficient usage of x86 addressing > modes in PIC. Looking into generated 32bit PIC assembler we may see lots of > 'leal @GOTOFF, %reg' instructions. Almost in all cases this > constant

[PATCH, PR target/65103, 1/3] Fix cost of PIC register in ix86_address_cost

2015-03-10 Thread Ilya Enkovich
Hi, This patches set addresses the problem of inefficient usage of x86 addressing modes in PIC. Looking into generated 32bit PIC assembler we may see lots of 'leal @GOTOFF, %reg' instructions. Almost in all cases this constant value may be propagated into following address operand, but it do