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++/98481] [10/11 Regression] std::vector<std::string>::size_type as return type gets tagged with abi:cxx11
Date: Thu, 07 Jan 2021 11:08:22 +0000	[thread overview]
Message-ID: <bug-98481-4-HhdgFviAJ3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98481-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
                 CC|                            |jakub at gcc dot gnu.org
   Last reconfirmed|                            |2021-01-07
     Ever confirmed|0                           |1

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
This boils down to:
inline namespace N __attribute ((__abi_tag__ ("cxx11")))
{
  struct A {};
}
template <typename T>
struct B { typedef int size_type; };
struct S1 { B<A>::size_type foo () const { return 1; } };
struct S2 { B<A>::size_type foo () const; };
int S2::foo () const { return 2; }

int
main ()
{
  auto f1 = &S1::foo;
  auto f2 = &S2::foo;
}

  parent reply	other threads:[~2021-01-07 11:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-30 17:25 [Bug c++/98481] New: " Daniel.Riley at cornell dot edu
2021-01-05 10:48 ` [Bug c++/98481] [10/11 Regression] " rguenth at gcc dot gnu.org
2021-01-07 11:08 ` jakub at gcc dot gnu.org [this message]
2021-01-07 11:13 ` jakub at gcc dot gnu.org
2021-01-07 11:13 ` jakub at gcc dot gnu.org
2021-01-07 11:39 ` jakub at gcc dot gnu.org
2021-01-07 12:01 ` jakub at gcc dot gnu.org
2021-01-11 16:15 ` cvs-commit at gcc dot gnu.org
2021-04-01 11:38 ` [Bug c++/98481] [10 " cvs-commit at gcc dot gnu.org
2021-04-01 14:05 ` cvs-commit at gcc dot gnu.org
2021-04-05 21:36 ` jason 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-98481-4-HhdgFviAJ3@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).