From: Savithri Venkatachalapathy <snvpathy@yahoo.com>
To: gcc-help@gcc.gnu.org
Subject: Question on .md file
Date: Mon, 22 Sep 2003 03:25:00 -0000 [thread overview]
Message-ID: <20030922032528.20718.qmail@web14204.mail.yahoo.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 1229 bytes --]
Hello All,
I am once again posting my question on the list and
hope to get some pointers regarding this.
A few questions about the .md file.
1.In the .md file I noticed that there are certain
instructions defined as: define_insn "aaa_internal1",
"aaa_internal2a" etc..
What does this actually mean? What does "internal"
suggest?
2. I have 4 brach instructions:
BNE (Branch on Not Equal)
BEQ (Branch on EQual)
BEQZ(Branch on EQual to Zero)
BNEZ(Branch on Not Equal to Zero)
I have defined the first 2 instructions as define_insn
"bne" and define_insn "beq".
But I am not sure which name I should use for the last
2 instructions.
3. Also I noticed in arm.md, sh.md, that the branch
instructions have define_expand and not define_insn.
Why is that?
I would really really appreciate any help in this
regard.
Thanks,
savi
=====
-------------------------------------------------------------------------------
Personality is born out of pain. It is the fire shut up in the flint. --- Yeats
--------------------------------------------------------------------------------
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
next reply other threads:[~2003-09-22 3:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-22 3:25 Savithri Venkatachalapathy [this message]
2003-09-22 3:49 ` Ian Lance Taylor
-- strict thread matches above, loose matches on Subject: below --
2003-09-21 5:01 Savithri Venkatachalapathy
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=20030922032528.20718.qmail@web14204.mail.yahoo.com \
--to=snvpathy@yahoo.com \
--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).