public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109232] Using deduced return type in an unevaluated context leads to codegen Date: Wed, 22 Mar 2023 14:21:42 +0000 [thread overview] Message-ID: <bug-109232-4-X6fE7pXHBu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109232-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109232 --- Comment #5 from Patrick Palka <ppalka at gcc dot gnu.org> --- So one workaround is to explicitly declare begin inline, which works because the problematic test in cgraph_node::finalize_function excludes DECL_DECLARED_INLINE_P functions.
prev parent reply other threads:[~2023-03-22 14:21 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-21 13:15 [Bug c++/109232] New: " rs2740 at gmail dot com 2023-03-21 13:26 ` [Bug c++/109232] " rguenth at gcc dot gnu.org 2023-03-21 14:39 ` pinskia at gcc dot gnu.org 2023-03-22 14:13 ` ppalka at gcc dot gnu.org 2023-03-22 14:16 ` ppalka at gcc dot gnu.org 2023-03-22 14:21 ` ppalka at gcc dot gnu.org [this message]
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-109232-4-X6fE7pXHBu@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).