From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: Jason Merrill <jason@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: G++ namespace association extension
Date: Tue, 17 Jul 2012 19:48:00 -0000 [thread overview]
Message-ID: <CAH6eHdSQJFsoqw_ZRPBMNWGddT3NKTV7TFTL2+2BXBOvEkQmwg@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1207160133480.5035@gerinyyl.fvgr>
[-- Attachment #1: Type: text/plain, Size: 616 bytes --]
On 16 July 2012 00:34, Gerald Pfeifer wrote:
> On Sun, 15 Jul 2012, Jonathan Wakely wrote:
>>> I think this also should go into the GCC 4.8 release notes
>>> (gcc-4.8/changes.html)?
>> I can do that too. There's no gcc-4.8 dir yet, do I need to copy over
>> the various other files from the gcc-4.7 dir or can I just create
>> changes.html and leave the RM to do the rest at the appropriate time?
>
> If you run `cvs up -PAd` it should magically appear. :-)
Ah yes, I'd (quite happily) forgotten how to use CVS, but have now
reinstated the ~/.cvsrc I used to have on my previous machine.
Here's what I committed.
[-- Attachment #2: ch.txt --]
[-- Type: text/plain, Size: 612 bytes --]
Index: changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.8/changes.html,v
retrieving revision 1.5
diff -u -r1.5 changes.html
--- changes.html 15 Jul 2012 21:24:31 -0000 1.5
+++ changes.html 17 Jul 2012 19:46:32 -0000
@@ -21,6 +21,9 @@
directory. The installation manual contains
more information about requirements to build GCC.</p>
+<p>The G++ namespace association extension, <code>__attribute ((strong))</code>,
+has been deprecated. Inline namespaces should be used instead.</p>
+
<h2>General Optimizer Improvements</h2>
<ul>
next prev parent reply other threads:[~2012-07-17 19:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAH6eHdSnLMvppxPPn5zajDn6HZ9n2f2YoYE6fGs7PB37rReJng@mail.gmail.com>
[not found] ` <4FFADA23.6050805@redhat.com>
2012-07-10 21:34 ` Jonathan Wakely
2012-07-10 23:26 ` Jason Merrill
2012-07-15 11:26 ` Gerald Pfeifer
2012-07-15 15:10 ` Jonathan Wakely
2012-07-15 23:34 ` Gerald Pfeifer
2012-07-17 19:48 ` Jonathan Wakely [this message]
2012-07-16 15:47 ` Jason Merrill
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=CAH6eHdSQJFsoqw_ZRPBMNWGddT3NKTV7TFTL2+2BXBOvEkQmwg@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=jason@redhat.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).