public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/95675] [8/9/10/11 Regression] internal compiler error: in build_over_call Date: Thu, 04 Mar 2021 04:49:29 +0000 [thread overview] Message-ID: <bug-95675-4-DtWCFNMT4z@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95675-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95675 --- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:371c7a82833df5d84392838cf2bf95b4da88655c commit r10-9414-g371c7a82833df5d84392838cf2bf95b4da88655c Author: Jason Merrill <jason@redhat.com> Date: Tue Mar 2 23:59:00 2021 -0500 c++: C++17 and decltype of multi-operator expression [PR95675] A call that is the immediate operand of decltype has special semantics: no temporary is produced, so it's OK for the return type to be e.g. incomplete. But we were treating (e | f) the same way, which confused overload resolution when we then tried to evaluate ... | g. Fixed by making build_temp do what its name says, and force the C++17 temporary materialization conversion. gcc/cp/ChangeLog: PR c++/95675 * call.c (build_temp): Wrap a CALL_EXPR in a TARGET_EXPR if it didn't get one before. gcc/testsuite/ChangeLog: PR c++/95675 * g++.dg/cpp0x/decltype-call5.C: New test. * g++.dg/cpp0x/decltype-call6.C: New test.
next prev parent reply other threads:[~2021-03-04 4:49 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-14 23:35 [Bug c++/95675] New: " rafael at espindo dot la 2020-06-14 23:35 ` [Bug c++/95675] " rafael at espindo dot la 2020-06-15 6:55 ` marxin at gcc dot gnu.org 2020-07-07 14:58 ` [Bug c++/95675] [8/9/10/11 Regression] " ppalka at gcc dot gnu.org 2020-07-07 14:58 ` ppalka at gcc dot gnu.org 2020-07-22 15:49 ` ppalka at gcc dot gnu.org 2020-08-12 12:25 ` ppalka at gcc dot gnu.org 2020-10-16 0:00 ` mpolacek at gcc dot gnu.org 2021-01-14 9:01 ` rguenth at gcc dot gnu.org 2021-02-10 15:03 ` ppalka at gcc dot gnu.org 2021-03-03 4:24 ` jason at gcc dot gnu.org 2021-03-03 13:47 ` cvs-commit at gcc dot gnu.org 2021-03-04 4:49 ` cvs-commit at gcc dot gnu.org [this message] 2021-03-04 5:13 ` cvs-commit at gcc dot gnu.org 2021-03-25 16:11 ` jason at gcc dot gnu.org 2021-04-02 13:30 ` ppalka 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-95675-4-DtWCFNMT4z@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).