public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/113994] Probable C++ code generation bug with -O2 on s390x platform Date: Mon, 19 Feb 2024 23:57:30 +0000 [thread overview] Message-ID: <bug-113994-4-SveGWcrH1f@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113994-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113994 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- I get g++ -O2 -o pr113994{,.C}; ./pr113994 terminate called after throwing an instance of 'std::out_of_range' what(): basic_string::substr: __pos (which is 3) > this->size() (which is 3) Aborted both with current trunk and with g++ 13.2.1 20231205 on real hw with the Fedora defaults, i.e. -march=z13 -mtune=z14.
next prev parent reply other threads:[~2024-02-19 23:57 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-19 15:01 [Bug c++/113994] New: " thierry at lelegard dot fr 2024-02-19 23:46 ` [Bug target/113994] " xry111 at gcc dot gnu.org 2024-02-19 23:57 ` jakub at gcc dot gnu.org [this message] 2024-02-20 8:08 ` rguenth at gcc dot gnu.org 2024-02-21 10:37 ` jakub at gcc dot gnu.org 2024-02-21 11:00 ` [Bug target/113994] [13/14 Regression] " jakub at gcc dot gnu.org 2024-02-21 12:25 ` jakub at gcc dot gnu.org 2024-02-29 10:17 ` stefansf at linux dot ibm.com 2024-02-29 10:23 ` jakub at gcc dot gnu.org 2024-02-29 12:00 ` rguenth at gcc dot gnu.org 2024-02-29 12:02 ` rguenth at gcc dot gnu.org 2024-02-29 12:04 ` jakub at gcc dot gnu.org 2024-02-29 12:59 ` rguenth at gcc dot gnu.org 2024-05-21 9:19 ` [Bug target/113994] [13/14/15 " jakub 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-113994-4-SveGWcrH1f@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).