This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: define_memory_constraint and REG_OK_STRICT
- From: Mohamed Shafi <shafitvm at gmail dot com>
- To: Richard Henderson <rth at redhat dot com>
- Cc: GCC <gcc at gcc dot gnu dot org>
- Date: Fri, 2 Oct 2009 17:33:25 +0530
- Subject: Re: define_memory_constraint and REG_OK_STRICT
- References: <ba0bd44d0909290732h2f5ca520q62f27bac2fe33f6c@mail.gmail.com> <4AC26501.6000001@redhat.com> <ba0bd44d0909292146q33174f6cv780894ba3795e203@mail.gmail.com> <4AC36E13.3090402@redhat.com>
2009/9/30 Richard Henderson <rth@redhat.com>:
> On 09/29/2009 09:46 PM, Mohamed Shafi wrote:
>>
>> ?bool strict = ?reload_completed ? true : false;
>
> What happens if you set "strict = false" here?
> That's what ARM does.
That particular case works, and yes arm does it that way but there
are other targets that uses (reload_completed || reload_in_progress)
like s390. So thats why i had to ask if my definition of strict is
proper or not. I am not sure which one to use?
Shafi