This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: glibc 2.21 - Master is frozen solid at -26 degC.
- From: David Miller <davem at davemloft dot net>
- To: carlos at redhat dot com
- Cc: libc-alpha at sourceware dot org, schwab at linux-m68k dot org, vapier at gentoo dot org, joseph at codesourcery dot com, azanella at linux dot vnet dot ibm dot com, krebbel at linux dot vnet dot ibm dot com, david dot holsgrove at xilinx dot com, chunglin_tang at mentor dot com, kkojima at rr dot iij4u dot or dot jp, thomas at codesourcery dot com, cmetcalf at tilera dot com, roland at hack dot frob dot com
- Date: Tue, 27 Jan 2015 15:56:11 -0800 (PST)
- Subject: Re: glibc 2.21 - Master is frozen solid at -26 degC.
- Authentication-results: sourceware.org; auth=none
- References: <54C71B4C dot 4070307 at redhat dot com>
From: "Carlos O'Donell" <carlos@redhat.com>
Date: Mon, 26 Jan 2015 23:59:56 -0500
> It's -26 degC in Deep River Ontario and the Ottawa river
> is frozen solid ... and so is master.
>
> Please TO: me on all patches and I'll ACK them throughout
> the day EST time.
>
> Manual fixes, obvious comment cleanups, and build fixes
> within machine-specific files are OK.
>
> Thank you to everyone who has already posted test results
> for your machine. Please keep testing.
>
> If you need help, please ask for it.
So I've got 32-bit sparcv9 and 64-bit sparc working by just blowing away
all of the existing sparc sem_*.c files.
I tried a pure 32-bit sparc build to start working on that part and I
get very non-helpful warnings (which are treated as errors) during the
NPTL build:
nptl-init.c: In function ʽsighandler_setxidʼ:
nptl-init.c:242:1: error: optimization may eliminate reads and/or writes to register variables [-Werror=volatile-register-var]
nptl-init.c:242:1: error: optimization may eliminate reads and/or writes to register variables [-Werror=volatile-register-var]
I get these all over the NPTL code, and every instance points to the
function's declaration rather than at any code within the function, which
makes tracking down what it's unhappy about not so easy.
I'll keep digging into this.