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++/114409] [14 Regression] ICE after adding novector pragmas (internal compiler error: in tsubst_expr, at cp/pt.cc:21794) since r14-4229-g9c62af101e11e1cce573c2b3d2e18b403412dbc8 Date: Wed, 10 Apr 2024 12:40:15 +0000 [thread overview] Message-ID: <bug-114409-4-xwU5Rnex0X@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114409-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114409 --- Comment #14 from Jakub Jelinek <jakub at gcc dot gnu.org> --- I had another look at this. The reason why this works without the pragmas (i.e. without ANNOTATE_EXPRs) is that the WHILE_COND/FOR_COND are handled not by tsubst_expr but tsubst_stmt: case FOR_STMT: stmt = begin_for_stmt (NULL_TREE, NULL_TREE); RECUR (FOR_INIT_STMT (t)); finish_init_stmt (stmt); tmp = RECUR (FOR_COND (t)); finish_for_cond (tmp, stmt, false, 0, false); and case WHILE_STMT: stmt = begin_while_stmt (); tmp = RECUR (WHILE_COND (t)); finish_while_stmt_cond (tmp, stmt, false, 0, false); in tsubst_stmt, where RECUR in that case means tsubst_stmt, not tsubst_expr. So, one possible fix is to use tsubst_stmt rather than RECUR aka tsubst_expr on the first operand of ANNOTATE_EXPR. And another would be to move the ANNOTATE_EXPR handling from tsubst_expr to tsubst_stmt.
next prev parent reply other threads:[~2024-04-10 12:40 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-20 21:02 [Bug c++/114409] New: ICE after adding novector pragmas (internal compiler error: in tsubst_expr, at cp/pt.cc:21794) sjames at gcc dot gnu.org 2024-03-20 21:05 ` [Bug c++/114409] " sjames at gcc dot gnu.org 2024-03-20 21:16 ` pinskia at gcc dot gnu.org 2024-03-20 21:21 ` pinskia at gcc dot gnu.org 2024-03-20 21:26 ` pinskia at gcc dot gnu.org 2024-03-20 21:29 ` sjames at gcc dot gnu.org 2024-03-21 9:37 ` rguenth at gcc dot gnu.org 2024-03-21 13:17 ` jakub at gcc dot gnu.org 2024-03-21 13:26 ` jakub at gcc dot gnu.org 2024-03-21 13:41 ` [Bug c++/114409] [14 Regression] " jakub at gcc dot gnu.org 2024-03-21 13:53 ` jakub at gcc dot gnu.org 2024-03-21 14:31 ` jakub at gcc dot gnu.org 2024-03-21 20:39 ` pinskia at gcc dot gnu.org 2024-04-10 7:58 ` [Bug c++/114409] [14 Regression] ICE after adding novector pragmas (internal compiler error: in tsubst_expr, at cp/pt.cc:21794) since r14-4229-g9c62af101e11e1cce573c2b3d2e18b403412dbc8 rguenth at gcc dot gnu.org 2024-04-10 12:40 ` jakub at gcc dot gnu.org [this message] 2024-04-10 12:49 ` jakub at gcc dot gnu.org 2024-04-10 12:50 ` jakub at gcc dot gnu.org 2024-04-11 7:48 ` cvs-commit at gcc dot gnu.org 2024-04-11 10:10 ` jakub at gcc dot gnu.org 2024-04-11 10:11 ` 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-114409-4-xwU5Rnex0X@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).