From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31823 invoked by alias); 20 Dec 2004 12:40:43 -0000 Mailing-List: contact glibc-bugs-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sources.redhat.com Received: (qmail 31705 invoked by uid 48); 20 Dec 2004 12:40:34 -0000 Date: Mon, 20 Dec 2004 12:40:00 -0000 Message-ID: <20041220124034.31704.qmail@sourceware.org> From: "jakub at redhat dot com" To: glibc-bugs@sources.redhat.com In-Reply-To: <20041022181914.467.mmazur@kernel.pl> References: <20041022181914.467.mmazur@kernel.pl> Reply-To: sourceware-bugzilla@sources.redhat.com Subject: [Bug libc/467] Build fails on sparc when gcc supports comdat X-Bugzilla-Reason: CC X-SW-Source: 2004-12/txt/msg00099.txt.bz2 List-Id: ------- 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.