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 d/109231] [13 regression] Comparison failure in libphobos/libdruntime/rt/util/typeinfo.o Date: Thu, 30 Mar 2023 16:22:51 +0000 [thread overview] Message-ID: <bug-109231-4-T9jjrOrKpy@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 #30 from Jakub Jelinek <jakub at gcc dot gnu.org> --- So, if I add the --- a/gcc/tree-inline.cc +++ b/gcc/tree-inline.cc @@ -2787,6 +2787,7 @@ 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); + aggregate_value_p (DECL_RESULT (new_fndecl), new_fndecl); /* We will rebuild these, so just sanity check that they are empty. */ gcc_assert (VALUE_HISTOGRAMS (cfun) == NULL); I see 5 calls of this in this spot, two with int return type, one with TFmode floating one, one with uint and one with bool. aggregate_value_p calls targetm.calls.return_in_memory but I don't see sparc_return_in_memory to have any side-effects other than return value. Next it calls reg = hard_function_value (type, 0, fntype, 0); which does allocate a REG rtx, but doesn't save it anywhere. It then calls fntype_abi and hard_regno_nregs and predefined_function_abi::clobbers_full_reg_p, but I don't see any side-effects in those either. Nothing seems to cache its results in any way. Confused...
next prev parent reply other threads:[~2023-03-30 16:22 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 [this message] 2023-03-30 18:17 ` jakub at gcc dot gnu.org 2023-03-31 7:57 ` ro at CeBiTec dot Uni-Bielefeld.DE 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-T9jjrOrKpy@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).