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++/99456] [11 regression] ABI breakage with some static initialization Date: Mon, 08 Mar 2021 13:39:50 +0000 [thread overview] Message-ID: <bug-99456-4-LSZnSgpAUI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99456-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99456 --- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> --- I'm not misreading the testcase, I'm just reacting on the fact that my patch changed the behavior of it and looking into related issues when analyzing why. It is up to the compiler to decide if it can or can't optimize it. The strange thing is that before my patch, it was actually triggerring the now removed cxx_eval_outermost_constant_expression code: /* Technically we should check this for all subexpressions, but that runs into problems with our internal representation of pointer subtraction and the 5.19 rules are still in flux. */ if (CONVERT_EXPR_CODE_P (TREE_CODE (r)) && ARITHMETIC_TYPE_P (TREE_TYPE (r)) && TREE_CODE (TREE_OPERAND (r, 0)) == ADDR_EXPR) { if (!allow_non_constant) error ("conversion from pointer type %qT " "to arithmetic type %qT in a constant expression", TREE_TYPE (TREE_OPERAND (r, 0)), TREE_TYPE (r)); non_constant_p = true; } but with allow_non_constant false. Which means the call didn't return (uintptr_t) &desc (the folded expression), but (uintptr_t) (unsigned int *) descRef (an unfolded one). And strangely that one then led to no dynamic initialization, while the folded one doesn't.
next prev parent reply other threads:[~2021-03-08 13:39 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-07 20:50 [Bug c++/99456] New: " nathan at gcc dot gnu.org 2021-03-07 20:51 ` [Bug c++/99456] " nathan at gcc dot gnu.org 2021-03-07 20:51 ` nathan at gcc dot gnu.org 2021-03-07 21:01 ` pinskia at gcc dot gnu.org 2021-03-08 9:56 ` rguenth at gcc dot gnu.org 2021-03-08 11:34 ` jakub at gcc dot gnu.org 2021-03-08 12:47 ` nathan at gcc dot gnu.org 2021-03-08 13:21 ` jakub at gcc dot gnu.org 2021-03-08 13:30 ` jakub at gcc dot gnu.org 2021-03-08 13:32 ` nathan at gcc dot gnu.org 2021-03-08 13:39 ` jakub at gcc dot gnu.org [this message] 2021-03-08 14:03 ` jakub at gcc dot gnu.org 2021-03-08 14:21 ` jakub at gcc dot gnu.org 2021-03-08 15:48 ` nathan at gcc dot gnu.org 2021-03-09 10:12 ` jakub at gcc dot gnu.org 2021-03-09 11:05 ` jakub at gcc dot gnu.org 2021-03-19 17:38 ` cvs-commit at gcc dot gnu.org 2021-03-19 17:38 ` jakub at gcc dot gnu.org 2021-03-22 2:09 ` unlvsur at live dot com
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-99456-4-LSZnSgpAUI@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).