From: Eric Botcazou <botcazou@adacore.com>
To: David Malcolm <dmalcolm@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: New "Diving into GCC internals" section in newbies guide
Date: Sat, 11 Jun 2022 02:35:24 +0200 [thread overview]
Message-ID: <5595934.DvuYhMxLoT@fomalhaut> (raw)
In-Reply-To: <b4633eea86dab10d656f11351563782dbcc36166.camel@redhat.com>
> Hope this is helpful; please let me know if you see any mistakes, or if
> there's room for improvement
Nice work! In the "inside cc1" chapter, I think that IR is usually meant for
"Intermediate Representation" rather than "Internal Representation" in this
context.
--
Eric Botcazou
next prev parent reply other threads:[~2022-06-11 0:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 21:58 David Malcolm
2022-06-11 0:35 ` Eric Botcazou [this message]
2022-06-12 16:37 ` David Malcolm
2022-06-12 17:11 ` Eric Gallager
2022-06-11 6:21 ` Sam James
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=5595934.DvuYhMxLoT@fomalhaut \
--to=botcazou@adacore.com \
--cc=dmalcolm@redhat.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).