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 c++/108833] [12 Regression] internal compiler error: Segmentation fault (GCC 12.1.1) Date: Fri, 17 Feb 2023 17:32:04 +0000 [thread overview] Message-ID: <bug-108833-4-8wfRkaoflt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108833-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108833 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Reduced testcase: struct input_t { template <class T> struct range_t { friend int &operator>>(int &, range_t &); range_t(char); }; int read_s; void read() { range_t<double> range(':'); read_s >> range; } }; int &operator>>(int &, input_t::range_t<double> &);
next prev parent reply other threads:[~2023-02-17 17:32 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-17 11:01 [Bug c++/108833] New: " liavonlida at gmail dot com 2023-02-17 11:50 ` [Bug c++/108833] [12 Regression] " rguenth at gcc dot gnu.org 2023-02-17 17:28 ` mpolacek at gcc dot gnu.org 2023-02-17 17:32 ` jakub at gcc dot gnu.org [this message] 2023-02-17 17:36 ` jakub at gcc dot gnu.org 2023-02-17 17:44 ` jakub at gcc dot gnu.org 2023-02-17 18:11 ` jakub at gcc dot gnu.org 2023-02-17 18:42 ` [Bug c++/108833] [11/12 " jakub at gcc dot gnu.org 2023-02-17 18:43 ` jakub at gcc dot gnu.org 2023-02-17 18:57 ` jakub at gcc dot gnu.org 2023-04-27 12:07 ` rguenth at gcc dot gnu.org 2023-05-29 10:08 ` 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-108833-4-8wfRkaoflt@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).