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: Question on INSN_P and "real" insns

From: Georg-Johann Lay <avr at gjlay dot de>
To: Eric Botcazou <ebotcazou at adacore dot com>
Cc: gcc at gcc dot gnu dot org
Date: Wed, 12 Oct 2011 11:44:04 +0200
Subject: Re: Question on INSN_P and "real" insns
References: <4E954CF4.20800@gjlay.de> <201110121130.20589.ebotcazou@adacore.com>

Eric Botcazou schrieb:
>> From my understanding a "real" insn is an insn that leads to code that will
>> be executed like INSN, CALL_INSN or JUMP_INSN but not DEBUG_INSN that's
>> used for location tracking or shipping debug information or CODE_LABEL or
>> whatever.
>>
>> This means that next_real_insn depends on -g? And that I have to write my
>> own next really_real_insn?
> 
> Try prev_active_insn/next_active_insn.

Ahh, yes. That looks fine. :-) Thanks Eric

References:
- Question on INSN_P and "real" insns
  - From: Georg-Johann Lay
- Re: Question on INSN_P and "real" insns
  - From: Eric Botcazou

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