public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug d/109231] [13 regression] Comparison failure in libphobos/libdruntime/rt/util/typeinfo.o Date: Fri, 31 Mar 2023 07:57:33 +0000 [thread overview] Message-ID: <bug-109231-4-66gQunQ1aa@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109231-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109231 --- Comment #32 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> --- > --- Comment #31 from Jakub Jelinek <jakub at gcc dot gnu.org> --- > If the important side-effect is allocation of some GC memory, then perhaps > (assuming you also see just 5 initialize_cfun calls with 2xint, TFmode float, > uint and bool) testing hack might be: I haven't verified this yet. > --- a/gcc/tree-inline.cc > +++ b/gcc/tree-inline.cc > @@ -2787,6 +2787,8 @@ initialize_cfun (tree new_fndecl, tree callee_fndecl, > profile_count count) > /* Get clean struct function. */ > push_struct_function (new_fndecl, true); > targetm.target_option.relayout_function (new_fndecl); > + if (INTEGRAL_TYPE_P (TREE_TYPE (DECL_RESULT (new_fndecl)))) > + gen_raw_REG (GET_MODE (TYPE_MODE (DECL_RESULT (new_fndecl))), 8); > > /* We will rebuild these, so just sanity check that they are empty. */ > gcc_assert (VALUE_HISTOGRAMS (cfun) == NULL); This doesn't compile as is: In file included from /var/gcc/reghunt/master/gcc/tree-inline.cc:26: /var/gcc/reghunt/master/gcc/tree-inline.cc: In function ‘void initialize_cfun(tree, tree, profile_count)’: /var/gcc/reghunt/master/gcc/rtl.h:728:54: error: base operand of ‘->’ is not a pointer 728 | #define GET_MODE(RTX) ((machine_mode) (RTX)->mode) | ^~ /var/gcc/reghunt/master/gcc/tree-inline.cc:2791:18: note: in expansion of macro ‘GET_MODE’ 2791 | gen_raw_REG (GET_MODE (TYPE_MODE (DECL_RESULT (new_fndecl))), 8); | ^~~~~~~~
next prev parent reply other threads:[~2023-03-31 7:57 UTC|newest] Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-21 12:42 [Bug d/109231] New: " ro at gcc dot gnu.org 2023-03-21 12:42 ` [Bug d/109231] " ro at gcc dot gnu.org 2023-03-21 12:49 ` jakub at gcc dot gnu.org 2023-03-21 12:58 ` ro at CeBiTec dot Uni-Bielefeld.DE 2023-03-21 14:02 ` jakub at gcc dot gnu.org 2023-03-21 14:36 ` ro at CeBiTec dot Uni-Bielefeld.DE 2023-03-21 15:16 ` jakub at gcc dot gnu.org 2023-03-21 15:18 ` ro at gcc dot gnu.org 2023-03-21 15:37 ` jakub at gcc dot gnu.org 2023-03-21 16:21 ` ro at CeBiTec dot Uni-Bielefeld.DE 2023-03-22 6:51 ` ro at CeBiTec dot Uni-Bielefeld.DE 2023-03-22 13:29 ` jakub at gcc dot gnu.org 2023-03-22 14:01 ` jakub at gcc dot gnu.org 2023-03-22 16:12 ` jakub at gcc dot gnu.org 2023-03-22 16:55 ` jakub at gcc dot gnu.org 2023-03-22 17:03 ` ro at CeBiTec dot Uni-Bielefeld.DE 2023-03-22 21:31 ` jakub at gcc dot gnu.org 2023-03-23 9:16 ` jakub at gcc dot gnu.org 2023-03-23 12:18 ` ro at CeBiTec dot Uni-Bielefeld.DE 2023-03-23 12:28 ` ro at CeBiTec dot Uni-Bielefeld.DE 2023-03-23 12:32 ` ro at CeBiTec dot Uni-Bielefeld.DE 2023-03-24 12:40 ` jakub at gcc dot gnu.org 2023-03-24 13:08 ` ro at CeBiTec dot Uni-Bielefeld.DE 2023-03-29 8:53 ` ro at CeBiTec dot Uni-Bielefeld.DE 2023-03-29 10:51 ` jakub at gcc dot gnu.org 2023-03-29 15:00 ` ro at CeBiTec dot Uni-Bielefeld.DE 2023-03-29 15:08 ` jakub at gcc dot gnu.org 2023-03-29 15:11 ` ro at CeBiTec dot Uni-Bielefeld.DE 2023-03-29 15:13 ` jakub at gcc dot gnu.org 2023-03-30 13:30 ` ro at CeBiTec dot Uni-Bielefeld.DE 2023-03-30 13:44 ` jakub at gcc dot gnu.org 2023-03-30 16:22 ` jakub at gcc dot gnu.org 2023-03-30 18:17 ` jakub at gcc dot gnu.org 2023-03-31 7:57 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message] 2023-03-31 7:59 ` jakub at gcc dot gnu.org 2023-03-31 9:22 ` ro at CeBiTec dot Uni-Bielefeld.DE 2023-03-31 9:26 ` jakub at gcc dot gnu.org 2023-03-31 12:15 ` ro at CeBiTec dot Uni-Bielefeld.DE 2023-03-31 12:28 ` jakub at gcc dot gnu.org 2023-04-17 15:14 ` [Bug d/109231] [13/14 " jakub at gcc dot gnu.org 2023-06-14 12:29 ` ro 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-109231-4-66gQunQ1aa@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).