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 target/98146] [11 Regression] section type conflict when "used" attribute is applied to decl with specific section
Date: Wed, 16 Dec 2020 13:43:44 +0000	[thread overview]
Message-ID: <bug-98146-4-17J0u0XjeX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98146-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by H.J. Lu <hjl@gcc.gnu.org>:

https://gcc.gnu.org/g:6175383249143309fdc780a02bea484f4450def7

commit r11-6140-g6175383249143309fdc780a02bea484f4450def7
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Thu Dec 3 11:01:06 2020 -0800

    Switch to a new section if the SECTION_RETAIN bit doesn't match

    When definitions marked with used attribute and unmarked definitions are
    placed in the section with the same name, switch to a new section if the
    SECTION_RETAIN bit doesn't match.

    gcc/

            PR target/98146
            * output.h (switch_to_section): Add a tree argument, default to
            nullptr.
            * varasm.c (get_section): If the SECTION_RETAIN bit doesn't match,
            return and switch to a new section later.
            (assemble_start_function): Pass decl to switch_to_section.
            (assemble_variable): Likewise.
            (switch_to_section): If the SECTION_RETAIN bit doesn't match,
            switch to a new section.

    gcc/testsuite/

            PR target/98146
            * c-c++-common/attr-used-5.c: New test.
            * c-c++-common/attr-used-6.c: Likewise.
            * c-c++-common/attr-used-7.c: Likewise.
            * c-c++-common/attr-used-8.c: Likewise.
            * c-c++-common/attr-used-9.c: Likewise.

  parent reply	other threads:[~2020-12-16 13:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-04 14:47 [Bug target/98146] New: " jozefl at gcc dot gnu.org
2020-12-07  7:49 ` [Bug target/98146] " rguenth at gcc dot gnu.org
2020-12-07 21:11 ` hjl.tools at gmail dot com
2020-12-11 15:41 ` hjl.tools at gmail dot com
2020-12-11 15:46 ` hjl.tools at gmail dot com
2020-12-16 13:43 ` cvs-commit at gcc dot gnu.org [this message]
2020-12-16 13:43 ` cvs-commit at gcc dot gnu.org
2020-12-16 13:43 ` cvs-commit at gcc dot gnu.org
2020-12-16 13:45 ` hjl.tools at gmail dot com

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-98146-4-17J0u0XjeX@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).