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>
Cc: Marcus Shawcroft <Marcus.Shawcroft@arm.com>
Subject: Re: Re: glibc 2.22 --- Stil frozen. Machine maintainers start testing.
Date: Tue, 28 Jul 2015 10:48:00 -0000	[thread overview]
Message-ID: <55B75DDB.4090305@arm.com> (raw)
In-Reply-To: <55AFB23E.5030908@arm.com>

On 22/07/15 16:09, Szabolcs Nagy wrote:
> 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:

i cannot edit
https://sourceware.org/glibc/wiki/Release/2.22

here is an update on a new toolchain:

gcc version 6.0.0 20150724 (experimental), aarch64-unknown-linux-gnu
GNU ld (GNU Binutils) 2.25.51.20150727
Linux 3.18.5 #1 SMP PREEMPT aarch64

XPASS: conform/ISO11/complex.h/conform
XPASS: conform/ISO11/stdalign.h/conform
XPASS: conform/ISO11/stdnoreturn.h/conform
FAIL: debug/tst-backtrace5
FAIL: debug/tst-backtrace6
FAIL: nptl/tst-stack4
Summary of test results:
       3 FAIL
    2252 PASS
      88 XFAIL
       3 XPASS

> 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.

still applies.

> other pending issues:
>
> 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.

this is the cause of nptl/tst-stack4 failure, it affects all archs,
it happens about once out of 100 runs here on aarch64.

Inconsistency detected by ld.so: dl-tls.c: 493: _dl_allocate_tls_init: 
Assertion `listp->slotinfo[cnt].gen <= _rtld_local._dl_tls_generation' 
failed!

> 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

i have a fix for this, not published yet.

  parent reply	other threads:[~2015-07-28 10:48 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
2015-07-23  6:23   ` Siddhesh Poyarekar
2015-07-28 10:48   ` Szabolcs Nagy [this message]
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=55B75DDB.4090305@arm.com \
    --to=szabolcs.nagy@arm.com \
    --cc=Marcus.Shawcroft@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).