public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/36282] [4.7/4.8 Regression] Spurious warning "asm declaration ignored due to conflict with previous rename"
Date: Thu, 10 Apr 2014 07:48:00 -0000	[thread overview]
Message-ID: <bug-36282-4-8Leu3paPOj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-36282-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36282

--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Thu Apr 10 07:47:55 2014
New Revision: 209263

URL: http://gcc.gnu.org/viewcvs?rev=209263&root=gcc&view=rev
Log:
    Backport from mainline
    2014-03-13  Jakub Jelinek  <jakub@redhat.com>

    PR middle-end/36282
    * c-pragma.c (apply_pragma_weak): Only look at
    TREE_SYMBOL_REFERENCED (DECL_ASSEMBLER_NAME (decl)) if
    DECL_ASSEMBLER_NAME_SET_P (decl).
    (maybe_apply_pending_pragma_weaks): Exit early if
    vec_safe_is_empty (pending_weaks) rather than only when
    !pending_weaks.
    (maybe_apply_pragma_weak): Likewise.  If !DECL_ASSEMBLER_NAME_SET_P,
    set assembler name back to NULL afterwards.

    * c-c++-common/pr36282-1.c: New test.
    * c-c++-common/pr36282-2.c: New test.
    * c-c++-common/pr36282-3.c: New test.
    * c-c++-common/pr36282-4.c: New test.

Added:
    branches/gcc-4_8-branch/gcc/testsuite/c-c++-common/pr36282-1.c
    branches/gcc-4_8-branch/gcc/testsuite/c-c++-common/pr36282-2.c
    branches/gcc-4_8-branch/gcc/testsuite/c-c++-common/pr36282-3.c
    branches/gcc-4_8-branch/gcc/testsuite/c-c++-common/pr36282-4.c
Modified:
    branches/gcc-4_8-branch/gcc/c-family/ChangeLog
    branches/gcc-4_8-branch/gcc/c-family/c-pragma.c
    branches/gcc-4_8-branch/gcc/testsuite/ChangeLog


  parent reply	other threads:[~2014-04-10  7:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-36282-4@http.gcc.gnu.org/bugzilla/>
2013-03-21 18:21 ` [Bug middle-end/36282] " aldot at gcc dot gnu.org
2013-04-11  8:00 ` [Bug middle-end/36282] [4.7/4.8/4.9 Regression] " rguenth at gcc dot gnu.org
2014-03-13 14:05 ` jakub at gcc dot gnu.org
2014-03-13 20:56 ` jakub at gcc dot gnu.org
2014-03-13 20:57 ` [Bug middle-end/36282] [4.7/4.8 " jakub at gcc dot gnu.org
2014-04-10  7:48 ` jakub at gcc dot gnu.org [this message]
2014-04-10  8:04 ` [Bug middle-end/36282] [4.7 " jakub at gcc dot gnu.org
2014-06-12 12:53 ` rguenth at gcc dot gnu.org
2014-06-12 12:53 ` rguenth at gcc dot gnu.org
2021-08-29 21:54 ` pinskia at gcc dot gnu.org
2021-12-22  2:09 ` pinskia 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-36282-4-8Leu3paPOj@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).