public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: Carlos O'Donell <carlos@redhat.com>,
	 GNU C Library <libc-alpha@sourceware.org>
Subject: Re: glibc 2.22 --- Stil frozen. Machine maintainers start testing.
Date: Wed, 22 Jul 2015 15:09:00 -0000	[thread overview]
Message-ID: <55AFB23E.5030908@arm.com> (raw)
In-Reply-To: <55AD56E4.4050903@redhat.com>

On 20/07/15 21:15, Carlos O'Donell wrote:
> This is a reminder that master is still frozen.
> 
> Only bug fixes and documentation patches.
> 
> Machine maintainers should *start* testing to make sure you 
> don't run into any unforseen problems.
> 
> I'd like to have the last bug fixes in by the end of the week.

aarch64 status:

FAIL: debug/tst-backtrace5
FAIL: debug/tst-backtrace6
there is a fix as part of the cancel changes:
https://sourceware.org/ml/libc-alpha/2015-06/msg00950.html
i can fix this independently, but i think it is ok
to delay this until next release and do it with the
cancellation fixes.

FAIL: elf/tst-protected1a
FAIL: elf/tst-protected1b
i'm testing a fix for gcc, binutils and glibc.
the glibc change is simple.
https://sourceware.org/bugzilla/show_bug.cgi?id=17711
https://sourceware.org/bugzilla/show_bug.cgi?id=18705
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66912

FAIL: math/test-double
FAIL: math/test-float
gcc bug, fixed for aarch64 in gcc-trunk
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66731

FAIL: stdio-common/bug22
this fails in my test environment, but it is a test bug.

other pending issues:

BZ 18572 Fix lazy tlsdesc race for arm.
i will work on this, but probably won't be in this release.

BZ 17918 dynamic-linker race: pthread_create can access
GL(dl_tls_max_dtv_idx) and GL(dl_tls_generation) without
holding the rtld lock.
https://sourceware.org/bugzilla/show_bug.cgi?id=17918
i don't know about any fix for this.

BZ 18707 aarch64 --enable-profile is broken because asm
for the mcount call clobbers registers it shouldn't.
https://sourceware.org/bugzilla/show_bug.cgi?id=18707

  reply	other threads:[~2015-07-22 15:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-20 20:15 Carlos O'Donell
2015-07-22 15:09 ` Szabolcs Nagy [this message]
2015-07-23  6:23   ` Siddhesh Poyarekar
2015-07-28 10:48   ` Szabolcs Nagy
2015-07-28 10:58     ` Siddhesh Poyarekar
2015-07-28 11:31     ` Mike Frysinger
2015-07-28 12:31       ` Szabolcs Nagy
2015-07-28 20:44     ` Carlos O'Donell
2015-07-29 10:24       ` Szabolcs Nagy
2015-07-23  5:53 ` Mike Frysinger
2015-07-23 19:55   ` Carlos O'Donell
2015-07-23 17:29 ` Carlos Eduardo Seo
2015-07-25 19:25 ` Jochen Hein
2015-07-27 17:54   ` Carlos O'Donell

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=55AFB23E.5030908@arm.com \
    --to=szabolcs.nagy@arm.com \
    --cc=carlos@redhat.com \
    --cc=libc-alpha@sourceware.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).