From: Andrew Haley <aph-gcc@littlepinkcloud.COM>
To: Nick Maclaren <nmm1@cus.cam.ac.uk>
Cc: gcc-help@gcc.gnu.org
Subject: Re: RTL obscurities
Date: Fri, 25 May 2007 13:32:00 -0000 [thread overview]
Message-ID: <18006.57700.862162.915960@zebedee.pink> (raw)
In-Reply-To: <E1HrZS7-0002Su-Gy@libra.cus.cam.ac.uk>
Nick Maclaren writes:
> I am trying to reverse engineer gcc's generation of RTL and failing
> dismally. Alll the documentation seems to be in terms of the
> string representation, and I can find nothing that links that to
> the relevant calls. I can find some calls, but nothing that will
> do what I need to two.
>
> And this is just to generate 3 instructions in the prologue!
>
> Can anyone help at all with this?
If course, but you haven't told us what you want to know. The
question above reads like a request for a detailed RTL cookbook and
manual, and you aren't going to get that in an email response.
Andrew.
next prev parent reply other threads:[~2007-05-25 13:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-25 13:15 Nick Maclaren
2007-05-25 13:32 ` Andrew Haley [this message]
2007-05-25 14:01 Nick Maclaren
2007-05-25 14:06 ` Andrew Haley
2007-05-25 19:27 ` Nick Maclaren
2007-05-25 16:46 ` 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=18006.57700.862162.915960@zebedee.pink \
--to=aph-gcc@littlepinkcloud.com \
--cc=gcc-help@gcc.gnu.org \
--cc=nmm1@cus.cam.ac.uk \
/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).