From: Paolo Carlini <paolo.carlini@oracle.com>
To: Peter Bergner <bergner@vnet.ibm.com>
Cc: Janis Johnson <janis_johnson@mentor.com>,
gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: PING [PATCH] Fix PR libstdc++/54036, problem negating DFP NaNs
Date: Fri, 03 Aug 2012 09:29:00 -0000 [thread overview]
Message-ID: <501B99D9.4020306@oracle.com> (raw)
In-Reply-To: <20120803000059.52337dce6ecbb94a42534bc5@vnet.ibm.com>
Hi,
On 08/03/2012 07:00 AM, Peter Bergner wrote:
> Fixed.
>
> Ok, once more with feeling! :) How about the updated patched below?
> ...and thank you for the gentle review. This is my first libstdc++
> patch and I guess I was used to the normal gcc/testsuite/ tests
> that don't include copyright headers and the like. I'll try to
> be more careful in the future.
No problem ;) Patch is Ok, thanks!
Paolo.
next prev parent reply other threads:[~2012-08-03 9:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 23:17 Peter Bergner
2012-08-01 14:00 ` Jason Merrill
2012-08-01 14:29 ` Paolo Carlini
2012-08-01 15:24 ` Janis Johnson
2012-08-01 23:54 ` Peter Bergner
2012-08-02 9:37 ` Paolo Carlini
2012-08-03 5:01 ` Peter Bergner
2012-08-03 9:29 ` Paolo Carlini [this message]
2012-08-13 22:15 ` Peter Bergner
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=501B99D9.4020306@oracle.com \
--to=paolo.carlini@oracle.com \
--cc=bergner@vnet.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=janis_johnson@mentor.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).