From: Sam James <sam@gentoo.org>
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 07:21:39 +0100 [thread overview]
Message-ID: <E5A9240F-6B35-4DBD-8140-4D4CC51334D1@gentoo.org> (raw)
In-Reply-To: <b4633eea86dab10d656f11351563782dbcc36166.camel@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 535 bytes --]
> On 10 Jun 2022, at 22:58, David Malcolm via Gcc <gcc@gcc.gnu.org> wrote:
>
> I've written a large new chunk of documentation for my GCC newbies
> guide, called "Diving into GCC internals", which can be seen at:
>
> https://gcc-newbies-guide.readthedocs.io/en/latest/diving-into-gcc-internals.html
>
> Hope this is helpful; please let me know if you see any mistakes, or if
> there's room for improvement
>
I didn't even realise the guide existed at all!
This looks really interesting, thanks!
> Dave
>
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 358 bytes --]
prev parent reply other threads:[~2022-06-11 6:25 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
2022-06-11 6:21 ` Sam James [this message]
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=E5A9240F-6B35-4DBD-8140-4D4CC51334D1@gentoo.org \
--to=sam@gentoo.org \
--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).