This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Why doesn't operand_equal_p check pointer equality first?
- From: Jeffrey A Law <law at redhat dot com>
- To: Richard Henderson <rth at redhat dot com>
- Cc: Diego Novillo <dnovillo at redhat dot com>, gcc at gcc dot gnu dot org
- Date: Thu, 12 May 2005 18:20:05 -0600
- Subject: Re: Why doesn't operand_equal_p check pointer equality first?
- References: <20050512171415.GA6176@topo.toronto.redhat.com> <20050512223738.GA8580@redhat.com>
- Reply-to: law at redhat dot com
On Thu, 2005-05-12 at 15:37 -0700, Richard Henderson wrote:
> On Thu, May 12, 2005 at 01:14:15PM -0400, Diego Novillo wrote:
> > Am I missing something here?
>
> Probably not.
Isn't operand_equal_p used in situations where we're eliminating
instructions -- and isn't the TREE_SIDE_EFFECT bit there to prevent
us from doing things like elimianting calls, volatiles and the like?
jeff