This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Address mode offset spill
- From: Jeff Law <law at redhat dot com>
- To: daniel tian <daniel dot xntian at gmail dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Tue, 30 Jun 2009 19:45:55 -0600
- Subject: Re: Address mode offset spill
- References: <121fadb80906140733g6b1eec5eg4ea945867f4affb7@mail.gmail.com> <m3y6rt8jne.fsf@google.com> <4A36B7A3.5040403@redhat.com> <121fadb80906170302p1d11a025g8ee03ca9ab4f9347@mail.gmail.com> <4A43DB0A.80003@redhat.com> <121fadb80906252033g14bd7cc5oa1df067fa81ae4a7@mail.gmail.com>
daniel tian wrote:
>> The compiler should work with or without defining LEGITIMIZE_RELOAD_ADDRESS.
>> It's often difficult to write a correct LEGITIMIZE_RELOAD_ADDRESS without
>> knowing the internals of how reload works. Therefore, I strongly recommend
>> first writing the port without LEGITIMIZE_RELOAD_ADDRESS -- after the port
>> is working correctly you can go back and add LEGITIMIZE_RELOAD_ADDRESS to
>> generate more efficient code.
>>
>>
>
> Do you mean that I should not write any reload code including
> secondary reload? And if it is going to work fine, then keep working
> on reload part?
>
You should write your secondary reload code, but not
LEGITIMIZE_RELOAD_ADDRESS.
After your port is working well, then define LEGITIMIZE_RELOAD_ADDRESS
to optimize the code better.
jeff