public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Denis.Excoffier at airbus dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/48179] New: Reference mismatch in documentation chapter 6
Date: Fri, 18 Mar 2011 13:32:00 -0000	[thread overview]
Message-ID: <bug-48179-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48179

           Summary: Reference mismatch in documentation chapter 6
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: minor
          Priority: P3
         Component: other
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: Denis.Excoffier@airbus.com


Bug in documentation presentation.

You can also try this under http://gcc.gnu.org/onlinedocs/gcc/

Jump to 6.37 "Specifying Attributes of Variables"
Click Next, you land on 6.38 "Specifying Attributes of Types". Fine.
Click Next, you land on 6.36 "Inquiring on Alignment of Types or Variables".
Strange.
Click Next, you land on 6.39 "An Inline Function Is...".

The table of content seems correct.

Also, on my texinfo gcc.info data base (from GCC 4.6.0 RC 20110314), but
not on onlinedocs, the reference (* note Variable Attributes::)
jumps to 6.37.1 "Blackfin Variable Attributes" instead
of 6.37.


             reply	other threads:[~2011-03-18 13:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-18 13:32 Denis.Excoffier at airbus dot com [this message]
2011-03-18 14:00 ` [Bug other/48179] " redi at gcc dot gnu.org
2011-03-22 13:38 ` redi at gcc dot gnu.org
2011-03-22 22:46 ` redi at gcc dot gnu.org
2011-03-23 20:01 ` redi at gcc dot gnu.org
2011-03-23 21:47 ` redi at gcc dot gnu.org
2011-03-23 21:47 ` redi at gcc dot gnu.org
2011-03-23 22:06 ` redi at gcc dot gnu.org
2011-03-27 21:08 ` redi at gcc dot gnu.org
2011-03-27 22:09 ` redi at gcc dot gnu.org

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=bug-48179-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).