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

From: Paolo Bonzini <bonzini at gnu dot org>
To: Mohamed Shafi <shafitvm at gmail dot com>
Cc: GCC <gcc at gcc dot gnu dot org>
Date: Tue, 29 Sep 2009 18:43:09 +0200
Subject: Re: define_memory_constraint and REG_OK_STRICT
References: <ba0bd44d0909290732h2f5ca520q62f27bac2fe33f6c@mail.gmail.com>

My question is my definition of strict correct?
or should it be reload_in_progress || reload_completed?

This is not my area of expertise, but "reload_completed" is definitely too weak.

I actually think strict should always be true when testing for satisfaction of constraints.

Paolo

References:
- define_memory_constraint and REG_OK_STRICT
  - From: Mohamed Shafi

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