public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jens.seifert at de dot ibm.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/94297] New: std::replace internal compiler error Date: Tue, 24 Mar 2020 10:02:03 +0000 [thread overview] Message-ID: <bug-94297-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94297 Bug ID: 94297 Summary: std::replace internal compiler error Product: gcc Version: 8.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: jens.seifert at de dot ibm.com Target Milestone: --- #include <algorithm> #include <string> void patch(std::string& s) { std::replace(s.begin(),s.end(),'.','-'); } gcc replace.C In file included from /opt/rh/devtoolset-8/root/usr/include/c++/8/bits/uniform_int_dist.h:35, from /opt/rh/devtoolset-8/root/usr/include/c++/8/bits/stl_algo.h:66, from /opt/rh/devtoolset-8/root/usr/include/c++/8/algorithm:62, from replace.C:1: /opt/rh/devtoolset-8/root/usr/include/c++/8/limits:1677:7: internal compiler error: Segmentation fault max() _GLIBCXX_USE_NOEXCEPT { return __DBL_MAX__; } ^~~ Please submit a full bug report, with preprocessed source if appropriate. See <http://bugzilla.redhat.com/bugzilla> for instructions. Preprocessed source stored into /tmp/ccFTVYLT.out file, please attach this to your bugreport.
next reply other threads:[~2020-03-24 10:02 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-24 10:02 jens.seifert at de dot ibm.com [this message] 2020-03-24 10:06 ` [Bug target/94297] PPCLE " jens.seifert at de dot ibm.com 2020-03-24 17:09 ` mpolacek at gcc dot gnu.org 2020-03-24 19:40 ` jens.seifert at de dot ibm.com 2020-03-24 20:12 ` mpolacek at gcc dot gnu.org 2020-03-24 20:30 ` jens.seifert at de dot ibm.com 2020-04-07 14:56 ` pinskia at gcc dot gnu.org 2020-04-07 17:11 ` jens.seifert at de dot ibm.com 2020-04-07 17:12 ` jens.seifert at de dot ibm.com 2020-04-07 17:14 ` jens.seifert at de dot ibm.com 2020-04-07 17:26 ` schwab@linux-m68k.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-94297-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).