public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Uros Bizjak <ubizjak@gmail.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Sandra Loosemore <sandra@codesourcery.com>
Subject: Re: [patch] rearrange attribute documentation sections
Date: Tue, 05 May 2015 17:35:00 -0000	[thread overview]
Message-ID: <CAFULd4a+2bGaUpjNg1Pzy3aiAMYkuB-oeUhefqOu_-GXm0F7Jw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 738 bytes --]

Hello!

> 2015-05-03  Sandra Loosemore  <sandra@codesourcery.com>
>
>    gcc/
>    * doc/extend.texi (Variable Attributes, Type Attributes):  Move
>    sections up in file, to immediately after the Function Attributes
>    section.

You also need to update relevant @menu entry, otherwise you get
several warning like:

/home/uros/gcc-svn/trunk/gcc/doc/extend.texi:2146: warning: node next
`Function Attributes' in menu `Label Attributes' and in sectioning
`Variable Attributes' differ

Fixed with attached patch.

2015-05-05  Uros Bizjak  <ubizjak@gmail.com>

    * doc/extend.texi (C Extensions): Update menu for moved Variable
    Attributes and Type Attributes sections.

Tested with texinfo 5.2 and committed to mainline SVN.

Uros.

[-- Attachment #2: d.diff.txt --]
[-- Type: text/plain, Size: 1220 bytes --]

Index: doc/extend.texi
===================================================================
--- doc/extend.texi	(revision 222816)
+++ doc/extend.texi	(working copy)
@@ -56,6 +56,8 @@
 * Mixed Declarations::  Mixing declarations and code.
 * Function Attributes:: Declaring that functions have no side effects,
                         or that they can never return.
+* Variable Attributes:: Specifying attributes of variables.
+* Type Attributes::     Specifying attributes of types.
 * Label Attributes::    Specifying attributes on labels.
 * Attribute Syntax::    Formal syntax for attributes.
 * Function Prototypes:: Prototype declarations and old-style definitions.
@@ -62,8 +64,6 @@
 * C++ Comments::        C++ comments are recognized.
 * Dollar Signs::        Dollar sign is allowed in identifiers.
 * Character Escapes::   @samp{\e} stands for the character @key{ESC}.
-* Variable Attributes:: Specifying attributes of variables.
-* Type Attributes::     Specifying attributes of types.
 * Alignment::           Inquiring about the alignment of a type or variable.
 * Inline::              Defining inline functions (as fast as macros).
 * Volatiles::           What constitutes an access to a volatile object.

             reply	other threads:[~2015-05-05 17:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-05 17:35 Uros Bizjak [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-05-04  2:53 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=CAFULd4a+2bGaUpjNg1Pzy3aiAMYkuB-oeUhefqOu_-GXm0F7Jw@mail.gmail.com \
    --to=ubizjak@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=sandra@codesourcery.com \
    /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).