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++/95222] [10/11 Regression] GCC 10.1 x86 issue with function pointers with calling convention attribute and template specialization
Date: Wed, 27 May 2020 14:10:27 +0000	[thread overview]
Message-ID: <bug-95222-4-SsiWbazvYr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95222-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jason Merrill <jason@gcc.gnu.org>:

https://gcc.gnu.org/g:7e7d9fcff56385812764cba63e1ebf6f4c6c0320

commit r11-662-g7e7d9fcff56385812764cba63e1ebf6f4c6c0320
Author: Jason Merrill <jason@redhat.com>
Date:   Mon May 25 19:04:05 2020 -0400

    c++: Fix stdcall attribute in template. [PR95222]

    Another case that breaks with my fix for PR90750: we shouldn't move type
    attributes in TYPENAME context either, as there's no decl for them to move
    to.

    gcc/cp/ChangeLog:

            PR c++/95222
            * decl.c (grokdeclarator): Don't shift attributes in TYPENAME
            context.

    gcc/testsuite/ChangeLog:

            PR c++/95222
            * g++.dg/ext/tmplattr10.C: New test.

  parent reply	other threads:[~2020-05-27 14:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-19 20:55 [Bug c++/95222] New: " raptorfactor at raptorfactor dot com
2020-05-19 20:57 ` [Bug c++/95222] " raptorfactor at raptorfactor dot com
2020-05-20  6:46 ` [Bug c++/95222] [10/11 Regression] " rguenth at gcc dot gnu.org
2020-05-23 20:44 ` jakub at gcc dot gnu.org
2020-05-25 22:54 ` jason at gcc dot gnu.org
2020-05-27 14:10 ` cvs-commit at gcc dot gnu.org [this message]
2020-05-27 14:11 ` cvs-commit at gcc dot gnu.org
2020-05-27 14:12 ` jason at gcc dot gnu.org
2020-05-28  7:46 ` ro at gcc dot gnu.org
2020-05-29 16:24 ` jason at gcc dot gnu.org
2022-01-03 15:37 ` puetzk at puetzk dot org
2022-01-03 22:01 ` puetzk at puetzk dot 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-95222-4-SsiWbazvYr@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).