public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: Sandra Loosemore <sandra@codesourcery.com>
Cc: Jonathan Wakely <jwakely.gcc@gmail.com>,
	       GCC Patches <gcc-patches@gcc.gnu.org>,
	       libstdc++ <libstdc++@gcc.gnu.org>,
	       Cesar Philippidis <cesar@codesourcery.com>
Subject: Re: [patch ping] libstdc++ testsuite cxxflags
Date: Tue, 20 May 2014 09:11:00 -0000	[thread overview]
Message-ID: <20140520091125.GN29145@redhat.com> (raw)
In-Reply-To: <537A7022.4090006@codesourcery.com>

On 19/05/14 14:57 -0600, Sandra Loosemore wrote:
>On 05/17/2014 04:07 AM, Jonathan Wakely wrote:
>>On 17 May 2014 10:50, Jonathan Wakely wrote:
>>>On 17 May 2014 01:16, Sandra Loosemore wrote:
>>>>It appears that this patch from last fall never got reviewed.
>>>>
>>>>https://gcc.gnu.org/ml/gcc-patches/2013-10/msg02340.html
>>>>
>>>>Can someone take a look?  I'll commit the patch on Cesar's behalf if it's
>>>>approved.
>>>
>>>Libstdc++ patches need to go to the libstdc++ list, which this did, in
>>>a separate mail that broke the threading:
>>>https://gcc.gnu.org/ml/libstdc++/2013-10/msg00224.html
>>>Then archives's inability to thread betweem months broke it again:
>>>https://gcc.gnu.org/ml/libstdc++/2013-11/msg00113.html
>>>
>>>I approved it then withdrew that approval:
>>>https://gcc.gnu.org/ml/libstdc++/2013-11/msg00120.html
>>>then the patch got revised:
>>>https://gcc.gnu.org/ml/libstdc++/2013-11/msg00122.html
>>>
>>>I'll have to refresh my memory about it.
>
>Whoops, I totally missed that there was already a separate thread on 
>the libstdc++ mailing list only.  My bad.  :-(
>
>>I think I'm happiest with the second version of the patch, in
>>https://gcc.gnu.org/ml/libstdc++/2013-11/msg00114.html
>>
>>It does mean a change that might affect people using CXXFLAGS when
>>running the tests, so we might want to update
>>https://gcc.gnu.org/onlinedocs/libstdc++/manual/test.html where it says
>>"Or, just run the testsuites with CXXFLAGS set to -D_GLIBCXX_DEBUG or
>>-D_GLIBCXX_PARALLEL."
>
>I came up with the attached patch for the wording change.  I'm having 
>trouble regenerating the HTML version of the manual, though; it looks 
>like I have a different version of the DocBook stylesheets around that 
>are introducing lots of extraneous changes, and I'm not sure what the 
>"right" version is.  :-S  Any suggestions?

You always get hundreds of changes, DocBook generates unique numeric
id attributes, which are different every run. Don't worr yabout the
docs, I can sort them out. If you and Cesar are happy with the patch
in https://gcc.gnu.org/ml/libstdc++/2013-11/msg00114.html then please
go ahead and commit that version, thanks.



  reply	other threads:[~2014-05-20  9:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-17  0:16 Sandra Loosemore
2014-05-17  4:56 ` Mike Stump
2014-05-17  9:50 ` Jonathan Wakely
2014-05-17  9:52   ` Jonathan Wakely
2014-05-17 10:07   ` Jonathan Wakely
2014-05-19 20:57     ` Sandra Loosemore
2014-05-20  9:11       ` Jonathan Wakely [this message]
2014-05-20 19:38         ` Cesar Philippidis
2014-05-24 16:07 David Edelsohn
2014-05-24 16:54 ` Jonathan Wakely
2014-05-25 19:16   ` David Edelsohn
2014-05-30  7:53   ` Ramana Radhakrishnan
2014-05-30 11:11     ` Jonathan Wakely

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=20140520091125.GN29145@redhat.com \
    --to=jwakely@redhat.com \
    --cc=cesar@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jwakely.gcc@gmail.com \
    --cc=libstdc++@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).