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 lto/105012] [12 Regression] wrf from SPECCPU2017 ICEs during LTO linking Date: Tue, 22 Mar 2022 10:52:39 +0000 [thread overview] Message-ID: <bug-105012-4-FLRTj1C3JA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105012-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105012 --- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> --- OK, so we have (gdb) p debug_gimple_stmt (stmt) derf(address-taken) ={v} {CLOBBER}; lacking virtual operands and the LHS is <function_decl 0x7ffff6346700 derf type <function_type 0x7ffff634a348 type <real_type 0x7ffff6537348 double DF ... that stmt is input this way from LTO bytecode. The following should catch who's building this. diff --git a/gcc/tree-cfg.cc b/gcc/tree-cfg.cc index e321d929fd0..fa92a505771 100644 --- a/gcc/tree-cfg.cc +++ b/gcc/tree-cfg.cc @@ -4512,7 +4512,8 @@ verify_gimple_assign_single (gassign *stmt) } if (gimple_clobber_p (stmt) - && !(DECL_P (lhs) || TREE_CODE (lhs) == MEM_REF)) + && !((DECL_P (lhs) && TREE_CODE (lhs) != FUNCTION_DECL) + || TREE_CODE (lhs) == MEM_REF)) { error ("%qs LHS in clobber statement", get_tree_code_name (TREE_CODE (lhs)));
next prev parent reply other threads:[~2022-03-22 10:52 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-22 8:54 [Bug lto/105012] New: " tnfchris at gcc dot gnu.org 2022-03-22 9:36 ` [Bug lto/105012] " marxin at gcc dot gnu.org 2022-03-22 10:21 ` rguenth at gcc dot gnu.org 2022-03-22 10:23 ` rguenth at gcc dot gnu.org 2022-03-22 10:37 ` marxin at gcc dot gnu.org 2022-03-22 10:52 ` rguenth at gcc dot gnu.org [this message] 2022-03-22 10:53 ` [Bug lto/105012] [12 Regression] wrf from SPECCPU2017 ICEs during LTO linking since r12-7692-g8db155ddf8cec9 marxin at gcc dot gnu.org 2022-03-22 10:58 ` marxin at gcc dot gnu.org 2022-03-22 11:06 ` [Bug fortran/105012] " rguenth at gcc dot gnu.org 2022-03-22 11:09 ` marxin at gcc dot gnu.org 2022-03-22 11:11 ` rguenth at gcc dot gnu.org 2022-03-22 11:18 ` rguenth at gcc dot gnu.org 2022-03-22 11:20 ` rguenth at gcc dot gnu.org 2022-03-22 11:31 ` rguenth at gcc dot gnu.org 2022-03-22 13:05 ` cvs-commit at gcc dot gnu.org 2022-03-22 13:07 ` rguenth at gcc dot gnu.org 2022-05-06 8:33 ` [Bug fortran/105012] [12/13 " jakub at gcc dot gnu.org 2022-08-24 19:36 ` anlauf at gcc dot gnu.org 2022-08-24 20:34 ` anlauf at gcc dot gnu.org 2022-08-25 6:13 ` rguenth at gcc dot gnu.org 2022-08-25 6:18 ` rguenth at gcc dot gnu.org 2022-08-25 19:50 ` mikael at gcc dot gnu.org 2022-08-25 19:55 ` anlauf at gcc dot gnu.org 2022-08-25 19:57 ` anlauf at gcc dot gnu.org 2022-08-25 20:06 ` mikael at gcc dot gnu.org 2022-08-25 20:30 ` anlauf at gcc dot gnu.org 2022-08-25 20:40 ` mikael at gcc dot gnu.org 2022-08-25 20:47 ` anlauf at gcc dot gnu.org 2022-08-25 21:19 ` mikael at gcc dot gnu.org 2022-08-25 21:31 ` anlauf at gcc dot gnu.org 2022-08-28 10:27 ` mikael at gcc dot gnu.org 2022-09-02 19:04 ` mikael at gcc dot gnu.org 2022-09-25 12:48 ` cvs-commit at gcc dot gnu.org 2022-09-25 12:48 ` cvs-commit at gcc dot gnu.org 2022-10-10 20:04 ` cvs-commit at gcc dot gnu.org 2022-10-10 20:53 ` cvs-commit at gcc dot gnu.org 2022-10-12 12:34 ` cvs-commit at gcc dot gnu.org 2022-10-12 12:42 ` mikael 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-105012-4-FLRTj1C3JA@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).