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]

Re: INSN_CODE_NUMBER of INT_MAX

To: Joern Rennecke <amylaar at redhat dot com>
Subject: Re: INSN_CODE_NUMBER of INT_MAX
From: Jan Hubicka <jh at suse dot cz>
Date: Thu, 26 Jul 2001 22:38:39 +0200
Cc: Jan Hubicka <jh at suse dot cz>, Richard Henderson <rth at redhat dot com>, Richard Kenner <kenner at vlsi1 dot ultra dot nyu dot edu>, gcc at gcc dot gnu dot org
References: <20010726222106.U9601@atrey.karlin.mff.cuni.cz> <200107262027.f6QKR4b25509@phal.cambridge.redhat.com>

> > The comment claims that the REG_EQUAL on noop move may be usefull later.
> > I don't think so (especially at combine time) so I suggest to blast that code.
> 
> No, definitely not.  These notes are useful for register allocation.
Uff, I see why now.

So sensible way is probably to modify combine to first try match, then
do the INT_MAX bypass and make delete_noop_move to blast INT_MAX insns
with notes and keep other noops lurking around...

Honza

References:
- Re: INSN_CODE_NUMBER of INT_MAX
  - From: Jan Hubicka
- Re: INSN_CODE_NUMBER of INT_MAX
  - From: Joern Rennecke

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