public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/110646] New: gensupport.cc:643:18: error: 'stoi' is not a member of 'std' Date: Wed, 12 Jul 2023 19:19:19 +0000 [thread overview] Message-ID: <bug-110646-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110646 Bug ID: 110646 Summary: gensupport.cc:643:18: error: 'stoi' is not a member of 'std' Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: danglin at gcc dot gnu.org CC: redi at gcc dot gnu.org Target Milestone: --- Host: hppa64-hp-hpux11.11 Target: hppa64-hp-hpux11.11 Build: hppa64-hp-hpux11.11 Created attachment 55532 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55532&action=edit Fix for build error. g++ -std=c++11 -c -g -DIN_GCC -fno-exceptions -fno-rtti -fasynchronous-unwi nd-tables -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wno-format -Wmiss ing-format-attribute -Wconditionally-supported -Woverloaded-virtual -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONFIG_H -DGENERATOR_FILE -I. -Ibuild -I../../gcc/gcc -I../../gcc/gcc/build -I../../gcc/gcc/../include -I../../gcc/gcc/../libcpp/include \ -o build/gensupport.o ../../gcc/gcc/gensupport.cc ../../gcc/gcc/gensupport.cc: In constructor 'conlist::conlist(const char*, unsigned int, bool)': ../../gcc/gcc/gensupport.cc:643:18: error: 'stoi' is not a member of 'std'; did you mean 'atoi'? 643 | idx = std::stoi (name); | ^~~~ | atoi Build gcc is: gcc version 12.2.1 20230420 [remotes/origin/releases/gcc-12 r12-9449-g3907147aa9 b] (GCC) 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.
next reply other threads:[~2023-07-12 19:19 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-12 19:19 danglin at gcc dot gnu.org [this message] 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 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@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: linkBe 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).