public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: John David Anglin <dave.anglin@bell.net>
Cc: Carlos O'Donell <carlos@redhat.com>,
	 GNU C Library <libc-alpha@sourceware.org>,
	 deller@kernel.org,  Mike Frysinger <vapier@gentoo.org>,
	 Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [PATCH] hppa: Optimize atomic_compare_and_exchange_val_acq
Date: Tue, 27 Sep 2016 22:50:00 -0000	[thread overview]
Message-ID: <87oa39vtxh.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <723790DF-7C85-4025-8087-AD0311DB1BA1@bell.net> (John David Anglin's message of "Tue, 27 Sep 2016 18:26:38 -0400")

* John David Anglin:

> On 2016-09-27, at 1:17 PM, Carlos O'Donell wrote:
>
>> Is the FAIL->PASS for tst-stack4 reliably tied to the addition of
>> this patch?
>
> I don't think so.  It has something to do with testsuite.  When I run
> test directly, it fails:
>
> dave@mx3210:~/gnu/glibc/objdir/nptl$ ./tst-stack4
> tst-stack4: tst-stack4.c:69: dso_process: Assertion `handle[dso]' failed.
> Didn't expect signal from child: got `Aborted'
>
>
> With gdb, I see:
>
> (gdb) r

Did you pass --direct?  The test harness spawns a subprocess.

  reply	other threads:[~2016-09-27 22:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-22 14:14 John David Anglin
2016-09-22 20:37 ` Carlos O'Donell
2016-09-22 21:38   ` Helge Deller
2016-09-27 17:15     ` Carlos O'Donell
2016-09-22 21:49   ` John David Anglin
2016-09-23  7:13     ` Florian Weimer
2016-09-27 17:17       ` Carlos O'Donell
2016-09-27 22:26         ` John David Anglin
2016-09-27 22:50           ` Florian Weimer [this message]
2016-09-27 23:04             ` John David Anglin
2016-09-28 20:29           ` Carlos O'Donell
2016-09-28 21:00           ` Florian Weimer
2016-10-02 16:47             ` John David Anglin
2016-10-12  5:24               ` 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=87oa39vtxh.fsf@mid.deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=aurelien@aurel32.net \
    --cc=carlos@redhat.com \
    --cc=dave.anglin@bell.net \
    --cc=deller@kernel.org \
    --cc=libc-alpha@sourceware.org \
    --cc=vapier@gentoo.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).