From: Jeff Law <jeffreyalaw@gmail.com>
To: John David Anglin <dave.anglin@bell.net>,
John David Anglin <dave@parisc-linux.org>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Use strtol instead of std::stoi in gensupport.cc
Date: Fri, 11 Aug 2023 09:11:31 -0600 [thread overview]
Message-ID: <1a5da2bd-512c-55b4-cf4e-dbe28eb422c9@gmail.com> (raw)
In-Reply-To: <e2ec5b09-ccec-91b2-9e13-56317826c68a@bell.net>
On 8/10/23 13:27, John David Anglin wrote:
> Ping.
>
> On 2023-07-19 2:59 p.m., John David Anglin wrote:
>> Tested on trunk with hppa64-hp-hpux11.11.
>>
>> Okay?
>>
>> Dave
>> ---
>>
>> Use strtol instead of std::stoi [PR110646]
>>
>> Implementation of std::stoi was overlooked on hppa-hpux, so use
>> strtol instead.
>>
>> 2023-07-19 John David Anglin <danglin@gcc.gnu.org>
>>
>> gcc/ChangeLog:
>>
>> PR bootstrap/110646
>> * gensupport.cc(class conlist): Use strtol instead of std::stoi.
OK. Sorry this got missed.
jeff
prev parent reply other threads:[~2023-08-11 15:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 18:59 John David Anglin
2023-08-10 19:27 ` John David Anglin
2023-08-11 15:11 ` Jeff Law [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=1a5da2bd-512c-55b4-cf4e-dbe28eb422c9@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=dave.anglin@bell.net \
--cc=dave@parisc-linux.org \
--cc=gcc-patches@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).