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]
Other format:	[Raw text]

Re: Use of INSN_CODE

From: "Steven Bosscher" <stevenb dot gcc at gmail dot com>
To: "Pranav Bhandarkar" <pranav dot bhandarkar at gmail dot com>
Cc: gcc at gcc dot gnu dot org
Date: Thu, 1 Feb 2007 10:50:07 +0100
Subject: Re: Use of INSN_CODE
References: <649555d50702010139r2738b78byc4e9d501ec8478a8@mail.gmail.com>

On 2/1/07, Pranav Bhandarkar <pranav.bhandarkar@gmail.com> wrote:

However, the internals  only warn against using INSN_CODE on use,
clobber, asm_input, addr_vec, addr_diff_vec. There is no mention of
other members of the other members of RTX_EXTRA. or shouldnt
recog_memoized have an INSN_P check in it ?
Am I missing something here ?

recog* should ice if what it gets passed is not an insn (i.e. !INSN_P).

Gr.
Steven

References:
- Use of INSN_CODE
  - From: Pranav Bhandarkar

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