This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: define_memory_constraint and REG_OK_STRICT


On 09/29/2009 07:32 AM, Mohamed Shafi wrote:
My question is my definition of strict correct?
or should it be reload_in_progress || reload_completed?

I'm tempted to say it should be the later, but I'm not sure it really makes any difference since reload does not query the operand predicates; it only queries the operand constraints.


And even that said, neither the ARM or IA64 ports do anything with strict at all, which suggests that you may not have to either. It's possible that this works because after reload we verify an instruction with both predicates and constraints.

Is this question in response to a particular problem, or just trying to avoid possible problems?


r~



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]