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++/107222] const qualifier appears in mangled NTTP value when the original object is so qualified
Date: Tue, 11 Oct 2022 20:07:09 +0000	[thread overview]
Message-ID: <bug-107222-4-vUGW55RXNl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107222-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2022-10-11
             Status|UNCONFIRMED                 |NEW
           Keywords|                            |ABI, wrong-code

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Here is one which shows the issue at link time.
This should link and run.
One testcase:
```
struct A { int i; };
union Y { A a; };
constexpr Y make_y(const A a) { return {a}; }
template<auto> struct q { };
template<auto V> constexpr q<V> make_q() { return {}; }
template<auto> void print();
template<> void print<q<(Y){.a={1}}>{}>()
{
}
int main() {
  constexpr q x = make_q<make_y({1})>();
  constexpr q x1 = make_q<(Y){.a={1}}>();
  print<x>();
  print<x1>();
}
```
Another one:
```
struct A { int i; };
union Y { A a; };
constexpr Y make_y(const A a) { return {a}; }
template<auto> struct q { };
template<auto V> constexpr q<V> make_q() { return {}; }
void print(q<(Y){.a={1}}> a)
{

}
void print(...);
int main() {
  constexpr q x = make_q<make_y({1})>();
  constexpr q x1 = make_q<(Y){.a={1}}>();
  print(x);
  print(x1);
}
```
clang mangles both x and x1 the same ...

      reply	other threads:[~2022-10-11 20:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-11 19:52 [Bug c++/107222] New: " johelegp at gmail dot com
2022-10-11 20:07 ` pinskia 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-107222-4-vUGW55RXNl@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).