From: Jonathan Wakely <jwakely@redhat.com>
To: Martin Sebor <msebor@gmail.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [patch] Leave errno unchanged by successful std::stoi etc
Date: Thu, 01 Oct 2015 11:24:00 -0000 [thread overview]
Message-ID: <20151001112421.GH12094@redhat.com> (raw)
In-Reply-To: <20150930132713.GE12094@redhat.com>
>commit 502928c8061343e82e982e06299c11d465f64b6c
>Author: Jonathan Wakely <jwakely@redhat.com>
>Date: Wed Sep 30 14:10:58 2015 +0100
>
> Save-and-restore errno more carefully in libstdc++
>
> * doc/xml/manual/diagnostics.xml: Document use of errno.
> * config/locale/generic/c_locale.cc (_Save_errno): New helper.
> (__convert_to_v): Use _Save_errno.
> * include/ext/string_conversions.h (__stoa): Only restore errno when
> it isn't set to non-zero.
>
Committed to trunk.
prev parent reply other threads:[~2015-10-01 11:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 15:55 Jonathan Wakely
2015-09-29 16:05 ` Jakub Jelinek
2015-09-29 16:25 ` Jonathan Wakely
2015-09-29 16:26 ` Jakub Jelinek
2015-09-29 17:28 ` Martin Sebor
2015-09-30 13:45 ` Jonathan Wakely
2015-10-01 11:24 ` Jonathan Wakely [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=20151001112421.GH12094@redhat.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=libstdc++@gcc.gnu.org \
--cc=msebor@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).