From: Jeff Bailey <jbailey@raspberryginger.com>
To: "Carlos O'Donell" <carlos@systemhalted.org>
Cc: parisc-linux <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] NPTL: The Bad News.
Date: Thu, 7 Sep 2006 08:54:28 -0700 [thread overview]
Message-ID: <20060907155428.GA5447@titanium.v3.ca> (raw)
In-Reply-To: <119aab440609061723r168cc628x3bf2dfb18bac1641@mail.gmail.com>
On Wed, Sep 06, 2006 at 08:23:18PM -0400, Carlos O'Donell wrote:
> The bad news is that I didn't work much on my thesis this long weekend.
> The good news is that I fixed many serious flaws related to:
>
> 1. Stack direction, stack guards, and stack permissions.
> 2. Low level locking primitives returning the wrong values.
> 3. EAGAIN != EWOULDBLOCK snafu's
> 4. Compiler bugs.
> 5. Makefile bugs.
>
> My current set of libc + tls + nptl failures is now down to:
Nice! I don't see these in CVS yet. Is there a branch or something
you're working on?
> make[2]: [libc-tls-nptl/posix/annexc.out] Error 1 (ignored)
Why is this under the "not cool" set? This is there for every arch.
> make[2]: *** [libc-tls-nptl/elf/tst-audit2.out] Error 139
Aside from the segfault, is the audit interface even written?
Tks,
Jeff Bailey
--
I do not agree with a word you say, but I will defend to the death your
right to say it.
- Voltaire
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2006-09-07 15:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-07 0:23 [parisc-linux] NPTL: The Bad News Carlos O'Donell
2006-09-07 15:54 ` Jeff Bailey [this message]
[not found] ` <119aab440609071009j12dc7daew199692707f1885d2@mail.gmail.com>
2006-09-07 23:13 ` Jeff Bailey
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=20060907155428.GA5447@titanium.v3.ca \
--to=jbailey@raspberryginger.com \
--cc=carlos@systemhalted.org \
--cc=parisc-linux@lists.parisc-linux.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