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++/51344] [4.4/4.5/4.6/4.7 regression] cc1plus hangs when compiling
Date: Thu, 29 Apr 2021 18:42:26 +0000 [thread overview]
Message-ID: <bug-51344-4-iks0s6sYXz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51344-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51344
--- Comment #11 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:a0fdff3cf33f72848d3f894272431a5d49fe6a16
commit r12-299-ga0fdff3cf33f72848d3f894272431a5d49fe6a16
Author: Jason Merrill <jason@redhat.com>
Date: Fri Feb 5 10:36:49 2021 -0500
c++: Fix friend attributes [PR51344]
51344 was a problem with calling save_template_attributes twice for the
same
friend function: once from do_friend and once from grokmethod. The 2012
patch for the bug avoided creating an infinite loop when this happens, but
it's better to avoid the duplication in the first place. This also
restores
the dependent attributes to the beginning of the attribute list, as
originally intended. And then apply_late_template_attributes can avoid
copying the non-dependent attributes.
gcc/cp/ChangeLog:
PR c++/51344
* decl2.c (grokfield): Call cplus_decl_attributes for friend.
(save_template_attributes): Use chainon.
* friend.c (do_friend): Remove attrlist parm.
* cp-tree.h (do_friend): Adjust.
* class.c (add_implicitly_declared_members): Adjust.
* decl.c (grokdeclarator): Adjust.
* pt.c (apply_late_template_attributes): Optimize.
next prev parent reply other threads:[~2021-04-29 18:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 14:06 [Bug c++/51344] New: " koliasvskj at gmail dot com
2011-11-29 14:33 ` [Bug c++/51344] " keithmarshall at mailinator dot com
2011-12-02 16:10 ` paolo.carlini at oracle dot com
2011-12-02 18:58 ` koliasvskj at gmail dot com
2012-01-17 11:24 ` ktietz at gcc dot gnu.org
2012-01-18 20:27 ` [Bug c++/51344] [4.4/4.5/4.6/4.7 regression] " jason at gcc dot gnu.org
2012-01-19 13:56 ` rguenth at gcc dot gnu.org
2012-01-19 22:29 ` ktietz at gcc dot gnu.org
2012-01-19 23:04 ` ktietz at gcc dot gnu.org
2012-01-19 23:09 ` ktietz at gcc dot gnu.org
2012-01-19 23:13 ` ktietz at gcc dot gnu.org
2012-01-19 23:16 ` ktietz at gcc dot gnu.org
2021-04-29 18:42 ` cvs-commit at gcc dot gnu.org [this message]
2022-01-27 21:55 ` cvs-commit 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-51344-4-iks0s6sYXz@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).