Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx> writes: > 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. ] > >> On Mon, Jul 10, 2023 at 3:01 PM Arsen Arsenović <arsen@xxxxxxxxx> wrote: >> > Sid Maxwell via Gcc-help <gcc-help@xxxxxxxxxxx> writes: >> > > Thank you, Segher. >> > > >> > > One thing that might be helpful would be, as I read the current "GNU >> > > Compiler Collection Internals >> > > For gcc version 14.0.0 (pre-release)", to compare it with the version of >> > > the same document that was relevant for 4.3.0. Do you know where I might >> > > learn which version is appropriate, and where I might find it? ( >> > > https://gcc.gnu.org/onlinedocs/ only seems to have the current version.) >> > >> > You should have received a copy in the info format in your gcc 4.3.0 >> > source tarball or distribution. > > 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). No, the distribution also contains gccint.info. > 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 -- Arsen Arsenović
Attachment:
signature.asc
Description: PGP signature
