public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: James E Wilson <wilson@specifix.com>
To: "Tabony, Charles" <ctabony@qualcomm.com>
Cc: gcc@gcc.gnu.org
Subject: Re: using recog_data.operand in ASM_OUTPUT_OPCODE
Date: Fri, 05 Aug 2005 02:53:00 -0000	[thread overview]
Message-ID: <42F2D4A0.4030005@specifix.com> (raw)
In-Reply-To: <EB1E62A76BB79847916C729925C820CE8A439B@NAEX06.na.qualcomm.com>

Tabony, Charles wrote:
> How can I
> distinguish recognized from unrecognized insns in ASM_OUTPUT_OPCODE?

Try using the variable this_is_asm_operands.

ASM_OUTPUT_OPCODE is an old macro that doesn't get used much anymore. 
FINAL_PRESCAN_INSN is better if you can use it.  No recog_data.operand 
trickery is needed here, as this one has the operands passed into it as 
a macro argument.  Or maybe you can use the two macros in combination to 
get the behaviour you need.
-- 
Jim Wilson, GNU Tools Support, http://www.specifix.com

      reply	other threads:[~2005-08-05  2:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-04 18:58 Tabony, Charles
2005-08-05  2:53 ` James E Wilson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42F2D4A0.4030005@specifix.com \
    --to=wilson@specifix.com \
    --cc=ctabony@qualcomm.com \
    --cc=gcc@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).