public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/102987] [9/10/11/12 Regression] Segfault when error or warning should trigger with combination. Date: Fri, 29 Oct 2021 06:38:51 +0000 [thread overview] Message-ID: <bug-102987-4-1eMBy3WI7F@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102987-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102987 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[9,10,11,trunk] Segfault |[9/10/11/12 Regression] |when error or warning |Segfault when error or |should trigger with |warning should trigger with |combination. |combination. Target Milestone|--- |9.5 Keywords| |diagnostic, | |ice-on-valid-code Priority|P3 |P2 Status|UNCONFIRMED |NEW Known to work| |8.5.0 Last reconfirmed| |2021-10-29 Ever confirmed|0 |1 --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- Confirmed. We have a VIEW_CONVERT_EXPR with NULL TREE_TYPE when dumping a TEMPLATE_DECL.
next prev parent reply other threads:[~2021-10-29 6:38 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-28 12:49 [Bug c++/102987] New: [9, 10, 11, trunk] " peeceseven at gmail dot com 2021-10-28 12:50 ` [Bug c++/102987] [9,10,11,trunk] " peeceseven at gmail dot com 2021-10-28 12:52 ` peeceseven at gmail dot com 2021-10-29 6:38 ` rguenth at gcc dot gnu.org [this message] 2022-04-14 21:39 ` [Bug c++/102987] [9/10/11/12 Regression] " jason at gcc dot gnu.org 2022-04-15 1:00 ` cvs-commit at gcc dot gnu.org 2022-04-29 13:21 ` [Bug c++/102987] [9/10/11 " cvs-commit at gcc dot gnu.org 2022-05-27 9:46 ` [Bug c++/102987] [10/11 " rguenth at gcc dot gnu.org 2022-06-28 10:46 ` jakub at gcc dot gnu.org 2023-07-07 10:41 ` [Bug c++/102987] [11 " rguenth 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-102987-4-1eMBy3WI7F@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).