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++/96078] [10 Regression] flatten attribute on constructor and destructor causes spurious warning
Date: Thu, 04 Mar 2021 04:49:23 +0000	[thread overview]
Message-ID: <bug-96078-4-GaaD1C8gLc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96078-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:d455130553544ee838b5215e76ccad22304cde39

commit r10-9413-gd455130553544ee838b5215e76ccad22304cde39
Author: Jason Merrill <jason@redhat.com>
Date:   Thu Feb 11 22:01:19 2021 -0500

    cgraph: flatten and same_body aliases [PR96078]

    The patch for PR92372 made us start warning about a flatten attribute on an
    alias.  But in the case of C++ 'tor base/complete variants, the user didn't
    create the alias.  If the alias target also has the attribute, the alias
    points to a flattened function, so we shouldn't warn.

    gcc/ChangeLog:

            PR c++/96078
            * cgraphunit.c (process_function_and_variable_attributes): Don't
            warn about flatten on an alias if the target also has it.
            * cgraph.h (symtab_node::get_alias_target_tree): New.

    gcc/testsuite/ChangeLog:

            PR c++/96078
            * g++.dg/ext/attr-flatten1.C: New test.

  parent reply	other threads:[~2021-03-04  4:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-06 13:15 [Bug c++/96078] New: [10/11 " rs2740 at gmail dot com
2020-07-06 13:35 ` [Bug c++/96078] " redi at gcc dot gnu.org
2020-07-06 15:31 ` rguenth at gcc dot gnu.org
2020-07-07  8:54 ` marxin at gcc dot gnu.org
2020-07-23  6:52 ` rguenth at gcc dot gnu.org
2020-10-12 12:49 ` rguenth at gcc dot gnu.org
2021-02-12  3:04 ` jason at gcc dot gnu.org
2021-02-12 17:10 ` jason at gcc dot gnu.org
2021-03-03  4:20 ` cvs-commit at gcc dot gnu.org
2021-03-03  4:22 ` [Bug c++/96078] [10 " jason at gcc dot gnu.org
2021-03-04  4:49 ` cvs-commit at gcc dot gnu.org [this message]
2021-03-04  4:52 ` jason at gcc dot gnu.org
2021-03-11 10:38 ` aoliva 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-96078-4-GaaD1C8gLc@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).