public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: Franck Bui-Huu <vagabon.xyz@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Clarification on section variable attribute usage [try #2]
Date: Tue, 11 Dec 2007 23:15:00 -0000	[thread overview]
Message-ID: <m363z4g6x0.fsf@localhost.localdomain> (raw)
In-Reply-To: <475EF29A.5060904@gmail.com>

Franck Bui-Huu <vagabon.xyz@gmail.com> writes:

> > Yes, I'm fairly sure that is no longer correct.  gcc is now smart
> > enough to not treat a variable with a section attribute as a common
> > variable.
> 
> Do you know when this happened ? Before GCC 3.2 ?

I don't know when it happened, no.

> > I think the documentation is simply wrong.
> 
> It's probably high time to fix it up.

Yep.

Ian

      reply	other threads:[~2007-12-11 23:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-10 20:59 Franck Bui-Huu
2007-12-11 16:17 ` Ian Lance Taylor
2007-12-11 20:27   ` Franck Bui-Huu
2007-12-11 23:15     ` Ian Lance Taylor [this message]

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=m363z4g6x0.fsf@localhost.localdomain \
    --to=iant@google.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=vagabon.xyz@gmail.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).