2009/3/2 daniel tian :
> 2009/2/27 daniel tian :
>> 2009/2/27 Dave Korn :
>>> daniel tian wrote:
>>>
That seems to solving a address mode problem. My problem is that while
loading a large immediate data or SYMBOL_REF, the destination is a
specified general register (register 0:R0).
2009/2/27 daniel tian :
> 2009/2/27 Dave Korn :
>> daniel tian wrote:
>>
>>> That seems to solving a address mode problem. My problem is that while
>>> loading a large immediate data or SYMBOL_REF, the destination is a
>>> specified general register (register 0:R0). So I don't how to let the
>>> d
2009/2/27 Dave Korn :
> daniel tian wrote:
>
>> That seems to solving a address mode problem. My problem is that while
>> loading a large immediate data or SYMBOL_REF, the destination is a
>> specified general register (register 0:R0). So I don't how to let the
>> define_expand "movsi" pattern to
daniel tian wrote:
> That seems to solving a address mode problem. My problem is that while
> loading a large immediate data or SYMBOL_REF, the destination is a
> specified general register (register 0:R0). So I don't how to let the
> define_expand "movsi" pattern to generate destination register
2009/2/27 Joern Rennecke :
> Quoting daniel tian :
>
>> 2009/2/26 Joern Rennecke :
the address label "common_reg " used many times. I think it will
load one time. But after optimized with '-Os' or '-O2', it still loads
the label "common_reg " six times..
>>>
>>> Previously, you
Quoting daniel tian :
2009/2/26 Joern Rennecke :
the address label "common_reg " used many times. I think it will
load one time. But after optimized with '-Os' or '-O2', it still loads
the label "common_reg " six times..
Previously, you could define LEGITIMIZE_ADDRESS and
LEGITIMIZE_RELOAD_AD
2009/2/26 Dave Korn :
> daniel tian wrote:
>
>> there is a 'movm' problem that puzzled me. In my target machine,
>> to load a large immediate data, can only move into zero register "R0".
>> but R0 is a generally register. I defined the the way in the
>> following:
>>
>> if the immediate dat
2009/2/26 Joern Rennecke :
>> the address label "common_reg " used many times. I think it will
>> load one time. But after optimized with '-Os' or '-O2', it still loads
>> the label "common_reg " six times..
>
> Previously, you could define LEGITIMIZE_ADDRESS and
> LEGITIMIZE_RELOAD_ADDRESS
> to ge
daniel tian wrote:
> there is a 'movm' problem that puzzled me. In my target machine,
> to load a large immediate data, can only move into zero register "R0".
> but R0 is a generally register. I defined the the way in the
> following:
>
> if the immediate data (op1) is larger than 1024
>
the address label "common_reg " used many times. I think it will
load one time. But after optimized with '-Os' or '-O2', it still loads
the label "common_reg " six times..
Previously, you could define LEGITIMIZE_ADDRESS and LEGITIMIZE_RELOAD_ADDRESS
to get reasonable code. However, that no long
hello,
there is a 'movm' problem that puzzled me. In my target machine,
to load a large immediate data, can only move into zero register "R0".
but R0 is a generally register. I defined the the way in the
following:
if the immediate data (op1) is larger than 1024
then do
{
11 matches
Mail list logo
