public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@redhat.com>
To: Eric Botcazou <botcazou@adacore.com>
Cc: gcc@gcc.gnu.org
Subject: Re: New "Diving into GCC internals" section in newbies guide
Date: Sun, 12 Jun 2022 12:37:01 -0400	[thread overview]
Message-ID: <10b942f07878e0b9b5a10230d40dc891fad02fc9.camel@redhat.com> (raw)
In-Reply-To: <5595934.DvuYhMxLoT@fomalhaut>

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
> 



  reply	other threads:[~2022-06-12 16:37 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 [this message]
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=10b942f07878e0b9b5a10230d40dc891fad02fc9.camel@redhat.com \
    --to=dmalcolm@redhat.com \
    --cc=botcazou@adacore.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).