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++/101180] [12 Regression] Rejected code since r12-299-ga0fdff3cf33f7284
Date: Thu, 25 Nov 2021 07:42:25 +0000 [thread overview]
Message-ID: <bug-101180-4-jOn9pXYJiM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101180-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101180
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:8e86218f05c1a866b43ae5af3e303f91fb6d7ff0
commit r12-5511-g8e86218f05c1a866b43ae5af3e303f91fb6d7ff0
Author: Jakub Jelinek <jakub@redhat.com>
Date: Thu Nov 25 08:39:35 2021 +0100
c++: Return early in apply_late_template_attributes if there are no late
attribs [PR101180]
The r12-299-ga0fdff3cf33f7284 change can result in cplus_decl_attributes
being called
even if there are no late attributes (but at least one early attribute) in
apply_late_template_attributes. This patch fixes that, so that we return
early
if there are no late attrs, only arrange for TYPE_ATTRIBUTES to get the
early
attribute list.
2021-11-25 Jakub Jelinek <jakub@redhat.com>
PR c++/101180
* pt.c (apply_late_template_attributes): Return early if there are
no
dependent attributes.
prev parent reply other threads:[~2021-11-25 7:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 13:05 [Bug c++/101180] New: " marxin at gcc dot gnu.org
2021-06-23 13:05 ` [Bug c++/101180] " marxin at gcc dot gnu.org
2021-11-18 18:01 ` jakub at gcc dot gnu.org
2021-11-18 18:26 ` jakub at gcc dot gnu.org
2021-11-19 21:10 ` cvs-commit at gcc dot gnu.org
2021-11-21 20:07 ` cvs-commit at gcc dot gnu.org
2021-11-22 9:58 ` jakub at gcc dot gnu.org
2021-11-25 7:42 ` cvs-commit 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-101180-4-jOn9pXYJiM@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).