From: Sid Maxwell <srmaxwell3@gmail.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: "Arsen Arsenović" <arsen@aarsen.me>, gcc-help@gcc.gnu.org
Subject: Re: Moving code generation from gcc 4.3.0 to gcc 12?
Date: Mon, 10 Jul 2023 16:31:55 -0400 [thread overview]
Message-ID: <CAGx9W7gfB8jG9_KjFcezmSZMwaD62TTy+6kPC3mYMPC6CMBDdw@mail.gmail.com> (raw)
In-Reply-To: <20230710200609.GW19790@gate.crashing.org>
[-- Attachment #1: Type: text/plain, Size: 1150 bytes --]
On Mon, Jul 10, 2023 at 4:11 PM Segher Boessenkool <
segher@kernel.crashing.org> wrote:
> On Mon, Jul 10, 2023 at 03:01:58PM -0400, Sid Maxwell wrote:
> > Of course, I should've thought of that. Thank you, Arsen!
>
> [ Please don't top-post. ]
>
> ...
>
> Not in the info format, those are binary files (.info files). Instead,
> the source code (in the doc/ directory) has the documentation in TeXinfo
> format (.texi files).
>
> https://gcc.gnu.org/onlinedocs/ has all versions going back to 2.95.3,
> just look a bit further down? :-)
>
> But yeah, just git log -p gcc/doc/ will tell you most. Maybe not in
> the best presentation for what you need -- but usually it is best to
> have multiple representations and use what most suitable in any
> particular situation :-)
>
>
> Segher
>
(Regarding top posting: I blame GMail, but only because I wasn't paying
attention.)
Thanks for the explanation. I'd looked at the online docs, but didn't see
"internals" mentioned except under "Current Development". Until you
mentioned .info/.texi, it hadn't occurred to me to look for gccint.texi.
:-)
-+- Sid
next prev parent reply other threads:[~2023-07-10 20:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 12:57 Sid Maxwell
2023-07-10 13:04 ` Jonathan Wakely
2023-07-10 14:34 ` Sid Maxwell
2023-07-10 17:13 ` Segher Boessenkool
2023-07-10 18:51 ` Sid Maxwell
2023-07-10 19:00 ` Arsen Arsenović
2023-07-10 19:01 ` Sid Maxwell
2023-07-10 20:06 ` Segher Boessenkool
2023-07-10 20:31 ` Sid Maxwell [this message]
2023-07-10 22:04 ` Arsen Arsenović
2023-07-10 22:29 ` Segher Boessenkool
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=CAGx9W7gfB8jG9_KjFcezmSZMwaD62TTy+6kPC3mYMPC6CMBDdw@mail.gmail.com \
--to=srmaxwell3@gmail.com \
--cc=arsen@aarsen.me \
--cc=gcc-help@gcc.gnu.org \
--cc=segher@kernel.crashing.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).