From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Andi Kleen <andi@firstfloor.org>,
gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: [PATCH] libstdc++: Fix up explicit-hle.cc test
Date: Tue, 22 Jan 2013 17:13:00 -0000 [thread overview]
Message-ID: <CAH6eHdSypTnL0eTR1J-aScMtGDQ3Ow_MQcgA3rMhvE0sweyXcQ@mail.gmail.com> (raw)
In-Reply-To: <20130122170044.GZ7269@tucnak.redhat.com>
On 22 January 2013 17:00, Jakub Jelinek wrote:
>
> Now in the form of a tested patch (regtested on x86_64-linux and
> i686-linux). Ok for trunk?
OK, thanks.
> dg-additional-options unfortunately isn't supported in libstdc++ testsuite,
> so had to use second dg-options, and also the \(, \) were wrong and resulted
> in no matches.
Kai has a forthcoming patch to add dg-additional-options:
http://gcc.gnu.org/ml/gcc-patches/2013-01/msg00945.html
next prev parent reply other threads:[~2013-01-22 17:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 6:06 [PATCH] libstdc++: Add mem_order_hle_acquire/release to atomic.h v2 Andi Kleen
2013-01-14 12:30 ` Jonathan Wakely
2013-01-21 14:06 ` Jakub Jelinek
2013-01-22 17:01 ` [PATCH] libstdc++: Fix up explicit-hle.cc test Jakub Jelinek
2013-01-22 17:13 ` Jonathan Wakely [this message]
2013-01-22 17:23 ` Andi Kleen
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=CAH6eHdSypTnL0eTR1J-aScMtGDQ3Ow_MQcgA3rMhvE0sweyXcQ@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=andi@firstfloor.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=libstdc++@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).