public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/110646] [14 Regression] gensupport.cc:643:18: error: 'stoi' is not a member of 'std'
Date: Wed, 12 Jul 2023 20:26:22 +0000	[thread overview]
Message-ID: <bug-110646-4-1lr6ouk8YZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110646-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110646

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to John David Anglin from comment #0)
> libstdc++ provides std::stoi in basic_string.h when _GLIBCXX_USE_C99_STDLIB
> is 1.  However, hpux11.11 lacks all the routines needed when
> _GLIBCXX_USE_C99_STDLIB is 1. But it does have strtol, atol, atoi, strtoul,
> strtod and atof.  strtoll and strtoull are not needed on hppa64 as long long
> and long are equivalent.  So it seems the string conversion routines could
> be provided in basic_string.h for this target.

Yes, those checks could be more granular.

I'll split out the checks needed for std::stoi etc.

  parent reply	other threads:[~2023-07-12 20:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-12 19:19 [Bug libstdc++/110646] New: " danglin at gcc dot gnu.org
2023-07-12 19:24 ` [Bug bootstrap/110646] [14 Regression] " pinskia at gcc dot gnu.org
2023-07-12 20:05 ` dave.anglin at bell dot net
2023-07-12 20:26 ` redi at gcc dot gnu.org [this message]
2023-07-12 20:31 ` redi at gcc dot gnu.org
2023-07-13  8:27 ` rguenth at gcc dot gnu.org
2023-07-13 10:00 ` redi at gcc dot gnu.org
2023-08-11 15:45 ` cvs-commit at gcc dot gnu.org
2023-08-11 15:54 ` danglin at gcc dot gnu.org

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=bug-110646-4-1lr6ouk8YZ@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).