From: "Bhaskar Reddy" <bhaskar@cse.iitb.ac.in>
To: gcc-help@gcc.gnu.org
Subject: Doubt about insn-codes and 'gencodes' program
Date: Fri, 09 Feb 2007 14:28:00 -0000 [thread overview]
Message-ID: <56436.10.129.41.10.1171028627.squirrel@www.cse.iitb.ac.in> (raw)
Hi,
After building gcc, in build/gcc, we can find insn-codes.h which contains,
enumeration 'insn_code' numbering of define_insn pattern by their name.
for some patterns, it contains value 'CODE_FOR_nothing' and for some
patterns it assigns an integer value.
For example:
#define CODE_FOR_extendhidi2 CODE_FOR_nothing
#define CODE_FOR_extendqidi2 CODE_FOR_nothing
CODE_FOR_extendhisi2 = 81,
CODE_FOR_extendqihi2 = 82,
CODE_FOR_extendqisi2 = 83,
CODE_FOR_truncxfsf2_i387_noop = 96,
CODE_FOR_truncxfdf2_i387_noop = 100,
i686-linux-gnu is the target machine, for which my compiler was build.
From the enum like above , How can i figure out which are the instructions
corresponding to 'i386' only.? [ as i386.md file was used for many other
cpu-types also, like pentium, k6 etc., am i getting this confusion! ]
TIA,
--
Bhaskar
next reply other threads:[~2007-02-09 13:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 14:28 Bhaskar Reddy [this message]
2007-02-09 17:40 ` Ian Lance Taylor
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=56436.10.129.41.10.1171028627.squirrel@www.cse.iitb.ac.in \
--to=bhaskar@cse.iitb.ac.in \
--cc=gcc-help@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).