public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aldot at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/37280] [4.4 Regression] weak symbol regression breaks linux kernel
Date: Tue, 16 Sep 2008 19:17:00 -0000	[thread overview]
Message-ID: <20080916191550.2450.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37280-7834@http.gcc.gnu.org/bugzilla/>



------- Comment #10 from aldot at gcc dot gnu dot org  2008-09-16 19:15 -------
(In reply to comment #9)
> Hi,
> 
>   I tried the following patch.
> http://gcc.gnu.org/ml/gcc-patches/2008-09/msg00195.html
> 
>   ".weak symbol" can be emitted, but with two same lines.  Thanks!

So that would bring you into the same situation as PR31537 is in (FE emits
duplicate asm directives, quick workaround in the BE for weakrefs is attached
to PR31537).


-- 


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


  parent reply	other threads:[~2008-09-16 19:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-29 15:13 [Bug other/37280] New: " ak at muc dot de
2008-08-29 16:03 ` [Bug other/37280] " andi-gcc at firstfloor dot org
2008-08-29 16:03 ` hp at gcc dot gnu dot org
2008-08-29 16:32 ` hp at gcc dot gnu dot org
2008-08-29 17:04 ` hp at gcc dot gnu dot org
2008-08-30 14:02 ` [Bug middle-end/37280] [4.4 Regression] " rguenth at gcc dot gnu dot org
2008-09-03 22:59 ` happyarch at gmail dot com
2008-09-03 23:25 ` hp at gcc dot gnu dot org
2008-09-04 23:08 ` happyarch at gmail dot com
2008-09-09 20:31 ` jsm28 at gcc dot gnu dot org
2008-09-16  1:13 ` chaoyingfu at gcc dot gnu dot org
2008-09-16 18:56 ` chaoyingfu at gcc dot gnu dot org
2008-09-16 19:17 ` aldot at gcc dot gnu dot org [this message]
2008-09-22  1:56 ` hp at gcc dot gnu dot org
2008-09-22  1:57 ` hp at gcc dot gnu dot org
2008-09-22  2:13 ` hp 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=20080916191550.2450.qmail@sourceware.org \
    --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).