From: Eric Gallager <egall@gwmail.gwu.edu>
To: David Malcolm <dmalcolm@redhat.com>
Cc: Eric Botcazou <botcazou@adacore.com>, GCC Development <gcc@gcc.gnu.org>
Subject: Re: New "Diving into GCC internals" section in newbies guide
Date: Sun, 12 Jun 2022 13:11:49 -0400 [thread overview]
Message-ID: <CAMfHzOuBKdDV+=bvKj7XUBQs4gTH_+mSOc4ZL8R4qaFn1qE-2Q@mail.gmail.com> (raw)
In-Reply-To: <10b942f07878e0b9b5a10230d40dc891fad02fc9.camel@redhat.com>
On Sun, Jun 12, 2022 at 12:38 PM David Malcolm via Gcc <gcc@gcc.gnu.org> wrote:
>
> On Sat, 2022-06-11 at 02:35 +0200, Eric Botcazou wrote:
> > > 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.
>
> Thanks - you're right. I've updated the doc accordingly.
>
> Dave
For the unwritten "What’s in the GCC source tree?" page I'd just like
to note that there's a similar page in the existing GCC internals docs
in sourcebuild.texi; I updated it recently in r13-817-gda5f0cc2f51a79:
https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=da5f0cc2f51a791a397fd1b3cef662763897a826
next prev parent reply other threads:[~2022-06-12 17:12 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
2022-06-12 16:37 ` David Malcolm
2022-06-12 17:11 ` Eric Gallager [this message]
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='CAMfHzOuBKdDV+=bvKj7XUBQs4gTH_+mSOc4ZL8R4qaFn1qE-2Q@mail.gmail.com' \
--to=egall@gwmail.gwu.edu \
--cc=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).