public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/32511] [4.4/4.5/4.6 regression] GCC rejects inline+weak function
Date: Tue, 11 Jan 2011 11:30:00 -0000	[thread overview]
Message-ID: <bug-32511-4-e7ill4Vsh2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-32511-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #14 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-01-11 10:09:19 UTC ---
Author: rguenth
Date: Tue Jan 11 10:09:15 2011
New Revision: 168652

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=168652
Log:
2011-01-12  Richard Guenther  <rguenther@suse.de>

    PR middle-end/32511
    * c-common.c (handle_weak_attribute): Warn instead of error
    on declaring an inline function weak.

    * gcc.dg/attr-weak-1.c: Adjust.

Modified:
    trunk/gcc/c-family/ChangeLog
    trunk/gcc/c-family/c-common.c
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/testsuite/gcc.dg/attr-weak-1.c


  parent reply	other threads:[~2011-01-11 10:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-32511-4@http.gcc.gnu.org/bugzilla/>
2010-09-30 11:56 ` rguenth at gcc dot gnu.org
2010-09-30 19:17 ` jason at gcc dot gnu.org
2011-01-10 15:49 ` matz at gcc dot gnu.org
2011-01-10 15:53 ` rguenth at gcc dot gnu.org
2011-01-11 11:30 ` rguenth at gcc dot gnu.org [this message]
2011-01-11 11:30 ` [Bug c/32511] [4.4/4.5 Regression] " rguenth at gcc dot gnu.org
2012-01-12 20:25 ` pinskia at gcc dot gnu.org
2012-03-13 15:02 ` [Bug c/32511] [4.5 " jakub at gcc dot gnu.org
2012-07-02  9:27 ` rguenth at gcc dot gnu.org
2007-06-26  5:30 [Bug c/32511] New: GCC inlines weak function sabre at nondot dot org
2010-07-12 13:46 ` [Bug c/32511] [4.4/4.5/4.6 regression] GCC rejects inline+weak function jason at gcc dot gnu dot 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-32511-4-e7ill4Vsh2@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).