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 10:08:46 -0700
- Cc: gcc at gcc dot gnu dot org
- References: <10107251104.AA04377@vlsi1.ultra.nyu.edu>
On Wed, Jul 25, 2001 at 07:04:03AM -0400, Richard Kenner wrote:
> I see the discussion in gcc-patches about this, but I don't see any of
> the above issues raise.
I'd forgotten about print-rtx, but I was actually _hoping_ that
extract_insn would blow up. As opposed to Jan's previous idea of
picking insn code 0, which belongs to someone else.
> I think this is a very bad idea: why not use the natural INSN_CODE
> for such moves?
There may not be one. We accept unrecognizable insns here.
r~