This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
INSN_CODE_NUMBER of INT_MAX
- To: gcc at gcc dot gnu dot org
- Subject: INSN_CODE_NUMBER of INT_MAX
- From: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- Date: Wed, 25 Jul 01 07:04:03 EDT
What is this about?
For one thing, you can't call debug_rtx on the insn since the code that
tries to print the insn code name blows up on it.
But I end up having that insn blow up in extract_insn for a similar
reason.
I see the discussion in gcc-patches about this, but I don't see any of
the above issues raise. I think this is a very bad idea: why not use the
natural INSN_CODE for such moves?