This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: INSN_CODE_NUMBER of INT_MAX
- To: Richard Kenner <kenner at vlsi1 dot ultra dot nyu dot edu>
- Subject: Re: INSN_CODE_NUMBER of INT_MAX
- From: Richard Henderson <rth at redhat dot com>
- Date: Thu, 26 Jul 2001 13:15:08 -0700
- Cc: gcc at gcc dot gnu dot org, jh at suse dot cz
- References: <10107262014.AA11402@vlsi1.ultra.nyu.edu>
On Thu, Jul 26, 2001 at 04:14:57PM -0400, Richard Kenner wrote:
> OK, then I see the bug. delete_noop_moves doesn't delete a nop insn that
> has a REG_EQUAL note. But such can *still* get the INT_MAX INSN_CODE.
> Indeed ths insn in question had that note.
>
> I'm not sure what was intended here.
I think this was due to some libcall lossage. Probably it shouldn't
be checking for REG_EQUAL but REG_RETVAL.
To be sure, INT_MAX should always be deleted. (Jan, I thought I
mentioned having a manifest constant NOOP_MOVE_INSN_CODE here?)
r~