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++/111284] [11/12/13/14 Regression] Some passing-by-value parameters are mishandled since GCC 9, affecting libstdc++'s constexpr std::string Date: Thu, 07 Mar 2024 18:58:12 +0000 [thread overview] Message-ID: <bug-111284-4-e3eWgwSFNu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111284-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111284 --- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Created attachment 57648 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57648&action=edit gcc14-pr111284.patch So, I've tried to fix this by constexpr evaluating the arguments passed to PARM_DECLs with TREE_ADDRESSABLE types in the caller as lvalues rather than rvaluea and later, if we try to evaluate the PARM_DECL in the callee as lval, lookup the value and use that, if it is rval constexpr evaluate again as rvalue. There is a complication for qualified type, say if the argument is const in the callee and caller is passing reference to non-const, adjust_temp_type can't handle that when it isn't a rvalue.
next prev parent reply other threads:[~2024-03-07 18:58 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-04 11:16 [Bug c++/111284] New: Some passing-by-value parameters are miscompiled since GCC 9 de34 at live dot cn 2023-09-05 14:37 ` [Bug c++/111284] [11/12/13/14 Regression] Some passing-by-value parameters are mishandled " mpolacek at gcc dot gnu.org 2023-09-05 14:37 ` mpolacek at gcc dot gnu.org 2023-09-05 18:00 ` jakub at gcc dot gnu.org 2023-09-05 18:04 ` jakub at gcc dot gnu.org 2023-09-05 19:21 ` jakub at gcc dot gnu.org 2023-09-05 19:27 ` jakub at gcc dot gnu.org 2023-09-11 11:32 ` jakub at gcc dot gnu.org 2023-09-11 12:12 ` jakub at gcc dot gnu.org 2024-03-07 18:58 ` jakub at gcc dot gnu.org [this message] 2024-03-11 15:12 ` [Bug c++/111284] [11/12/13/14 Regression] Some passing-by-value parameters are mishandled since GCC 9, affecting libstdc++'s constexpr std::string ppalka at gcc dot gnu.org 2024-04-25 18:46 ` cvs-commit at gcc dot gnu.org 2024-04-25 18:48 ` [Bug c++/111284] [11/12/13 " jakub at gcc dot gnu.org 2024-05-09 4:26 ` cvs-commit at gcc dot gnu.org 2024-05-09 8:17 ` [Bug c++/111284] [11/12 " 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-111284-4-e3eWgwSFNu@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).