public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at redhat dot com" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/467] Build fails on sparc when gcc supports comdat
Date: Mon, 20 Dec 2004 12:40:00 -0000	[thread overview]
Message-ID: <20041220124034.31704.qmail@sourceware.org> (raw)
In-Reply-To: <20041022181914.467.mmazur@kernel.pl>


------- Additional Comments From jakub at redhat dot com  2004-12-20 12:40 -------
Well, both GCC 3.3.4 and 3.4.0 for
volatile unsigned char __sparc32_atomic_locks[64]
__attribute__ ((nocommon, section (".gnu.linkonce.b.__sparc32_atomic_locks"),
                visibility ("hidden")));
generate
.section        ".gnu.linkonce.b.__sparc32_atomic_locks",#alloc,#write
and not what you wrote, so what the code does ATM is really needed, otherwise
the whole .bss section becomes SHT_PROGBITS.

Even current gcc-3_4-branch sparc.c has /* ??? Handle SECTION_BSS.  */
in sparc_elf_asm_named_section and so does GCC HEAD (and I don't see how
CVS GCC even does anything about comdat groups on SPARC at all).
So my guess is you are using some local hack.

So you clearly are us

-- 


http://sources.redhat.com/bugzilla/show_bug.cgi?id=467

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2004-12-20 12:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-22 18:19 [Bug libc/467] New: " mmazur at kernel dot pl
2004-10-30 22:00 ` [Bug libc/467] " mmazur at kernel dot pl
2004-12-19 14:27 ` aj at suse dot de
2004-12-20 12:40 ` jakub at redhat dot com [this message]
2004-12-20 12:42 ` jakub at redhat dot com
2004-12-20 12:52 ` jakub at redhat dot com
2004-12-20 15:00 ` mmazur at kernel dot pl
2010-06-01  1:59 ` pasky at suse dot cz

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=20041220124034.31704.qmail@sourceware.org \
    --to=sourceware-bugzilla@sources.redhat.com \
    --cc=glibc-bugs@sources.redhat.com \
    /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).