public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/105734] Regression: Incorrect "error: invalid use of 'auto'"
Date: Thu, 26 May 2022 05:03:40 +0000	[thread overview]
Message-ID: <bug-105734-4-MwXSlWIBhY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105734-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105734

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #2)
> Reduced testcase:
> namespace hh {
>     struct nothing {};
>     template<typename A = int>
>     struct expression_decomposer {
>         auto h()  {
>             return expression_decomposer<bool>();
>         }
>     };
> }
> 
> template <typename T>
> void bar() {
>         auto m = hh::expression_decomposer( hh::expression_decomposer{}.h());
>         m.~expression_decomposer();
> }
> 
> void foo() { bar<int>(); }

The namespace is really required here. If I remove it, it works ...

  parent reply	other threads:[~2022-05-26  5:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-26  4:30 [Bug c++/105734] New: " llvm at rifkin dot dev
2022-05-26  4:46 ` [Bug c++/105734] " llvm at rifkin dot dev
2022-05-26  5:03 ` pinskia at gcc dot gnu.org
2022-05-26  5:03 ` pinskia at gcc dot gnu.org [this message]
2022-05-26  5:05 ` [Bug c++/105734] [12/13 Regression]: Incorrect "error: invalid use of 'auto'" for explicit destructor inside a template pinskia at gcc dot gnu.org
2022-05-26  5:07 ` pinskia at gcc dot gnu.org
2022-05-26  5:09 ` pinskia at gcc dot gnu.org
2022-05-26  7:42 ` redi at gcc dot gnu.org
2022-05-26  7:59 ` redi at gcc dot gnu.org
2022-05-26 15:34 ` llvm at rifkin dot dev
2022-05-27  2:32 ` llvm at rifkin dot dev
2022-05-27  6:27 ` rguenth at gcc dot gnu.org
2022-05-31 20:25 ` jason at gcc dot gnu.org
2022-06-01 19:21 ` cvs-commit at gcc dot gnu.org
2022-06-01 19:53 ` cvs-commit at gcc dot gnu.org
2022-06-01 19:54 ` jason at gcc dot gnu.org
2022-06-01 23:13 ` llvm at rifkin dot dev

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-105734-4-MwXSlWIBhY@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: link
Be 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).