On Tue, May 8, 2012 at 4:05 PM, Richard Henderson wrote:
> On 05/06/2012 11:41 AM, Richard Sandiford wrote:
>>
>> PR middle-end/53249
>> * dwarf2out.h (get_address_mode): Move declaration to...
>> * rtl.h: ...here.
>> * dwarf2out.c (get_address_mode): Move definition to
On 05/06/2012 11:41 AM, Richard Sandiford wrote:
PR middle-end/53249
* dwarf2out.h (get_address_mode): Move declaration to...
* rtl.h: ...here.
* dwarf2out.c (get_address_mode): Move definition to...
* rtlanal.c: ...here.
* var-tracking.c (get_addre
On Sun, May 6, 2012 at 11:41 AM, Richard Sandiford
wrote:
> x32 uses a mixture of MEM address modes for the same address space.
> Some MEMs have SImode addresses, some have DImode. This means that
> the currently common idiom:
>
> targetm.addr_space.address_mode (MEM_ADDR_SPACE (mem))
>
> isn'
On Sun, May 6, 2012 at 11:41 AM, Richard Sandiford
wrote:
> x32 uses a mixture of MEM address modes for the same address space.
> Some MEMs have SImode addresses, some have DImode. This means that
> the currently common idiom:
>
> targetm.addr_space.address_mode (MEM_ADDR_SPACE (mem))
>
> isn'
"H.J. Lu" writes:
>> Index: gcc/sel-sched-dump.c
>> ===
>> --- gcc/sel-sched-dump.c 2012-05-06 16:17:20.0 +0100
>> +++ gcc/sel-sched-dump.c 2012-05-06 16:17:20.316206160 +0100
>> @@ -957,7 +957,7 @@ debug_mem_add
On Sun, May 6, 2012 at 11:41 AM, Richard Sandiford
wrote:
> x32 uses a mixture of MEM address modes for the same address space.
> Some MEMs have SImode addresses, some have DImode. This means that
> the currently common idiom:
>
> targetm.addr_space.address_mode (MEM_ADDR_SPACE (mem))
>
> isn'
On Sun, May 6, 2012 at 11:41 AM, Richard Sandiford
wrote:
> x32 uses a mixture of MEM address modes for the same address space.
> Some MEMs have SImode addresses, some have DImode. This means that
> the currently common idiom:
>
> targetm.addr_space.address_mode (MEM_ADDR_SPACE (mem))
>
> isn'
x32 uses a mixture of MEM address modes for the same address space.
Some MEMs have SImode addresses, some have DImode. This means that
the currently common idiom:
targetm.addr_space.address_mode (MEM_ADDR_SPACE (mem))
isn't trustworthy. We have to use the mode of the address if it has one,