From: Sandra Loosemore <sandra@codesourcery.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: [doc, 4/n] invoke.texi: there is no part 4
Date: Fri, 15 Jan 2016 02:00:00 -0000 [thread overview]
Message-ID: <569852D1.100@codesourcery.com> (raw)
In-Reply-To: <5692EE28.1070502@codesourcery.com>
Part 4 of this series was originally intended to move the section "Using
Precompiled Headers" from invoke.texi to extend.texi. But, as I started
to dig around to decide exactly where its should go, I didn't see a good
place to put it there, either -- extend.texi is still very disorganized.
I've decided to leave the section where it is for now.
In the long run, I think maybe it should be grouped with other
documentation describing preprocessor extensions, since it is
essentially describing an extension to #include.
-Sandra
next prev parent reply other threads:[~2016-01-15 2:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-10 23:50 [doc, 0/n] improve organization of invoke.texi Sandra Loosemore
2016-01-12 17:45 ` [doc, 1/n] invoke.texi: name of gcc executable Sandra Loosemore
2016-01-13 0:48 ` [doc, 1.5/n] invoke.texi: reclassify -no-canonical-prefixes and -specs= Sandra Loosemore
2016-01-13 3:31 ` [doc, 2/n] invoke.texi: move spec file section Sandra Loosemore
2016-01-13 21:08 ` [doc, 3/n] invoke.texi: move "Code Gen Options" before target-specific options Sandra Loosemore
2016-01-25 0:16 ` Gerald Pfeifer
2016-01-13 23:38 ` [doc, 3.5/n] invoke.texi: rename "Machine-Dependent Options" section Sandra Loosemore
2016-01-15 2:00 ` Sandra Loosemore [this message]
2016-01-15 2:18 ` [doc, 5/n] invoke.texi: add new "Program Instrumentation " Sandra Loosemore
2016-01-15 8:39 ` Mikhail Maltsev
2016-01-15 15:52 ` Sandra Loosemore
2016-01-17 4:12 ` [doc, 6/n] invoke.texi: split debugging options into programmer vs developer sections Sandra Loosemore
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=569852D1.100@codesourcery.com \
--to=sandra@codesourcery.com \
--cc=gcc-patches@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).