From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
dave.anglin@nrc-cnrc.gc.ca, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] r19 (aka pic-register akak ltp) not restored on
Date: Fri, 19 Sep 2003 15:28:13 -0400 [thread overview]
Message-ID: <20030919192813.GL18225@systemhalted> (raw)
In-Reply-To: <200309191855.h8JItUaf003758@hiauly1.hia.nrc.ca>
On Fri, Sep 19, 2003 at 02:55:30PM -0400, John David Anglin wrote:
> > On Fri, 2003-09-19 at 12:51, Carlos O'Donell wrote:
> > > mutex_unlock becomes:
> > > __libc_maybe_call (__pthread_mutex_unlock, (m), (*(int *)(m) = 0))
> >
> > This seems all to work:
>
> Yah, the normal code that gcc generates to restore the ltp is very
> extensively tested. Shared libraries would break almost instantly
> if there were major problems.
>
If it were major we would have fixed it :)
I'm trying to find the "missed a restore" point.
c.
next prev parent reply other threads:[~2003-09-19 19:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-19 13:56 [parisc-linux] r19 (aka pic-register akak ltp) not restored on entry back to libc from libpthread? Carlos O'Donell
2003-09-19 16:56 ` John David Anglin
2003-09-19 17:51 ` Carlos O'Donell
2003-09-19 18:26 ` James Bottomley
2003-09-19 18:55 ` [parisc-linux] r19 (aka pic-register akak ltp) not restored on John David Anglin
2003-09-19 19:28 ` Carlos O'Donell [this message]
2003-09-19 20:10 ` John David Anglin
2003-09-21 15:45 ` [parisc-linux] Found the r19 problem! Carlos O'Donell
2003-09-21 16:39 ` [parisc-linux] " John David Anglin
2003-09-21 18:53 ` Carlos O'Donell
2003-09-21 18:55 ` Carlos O'Donell
2003-09-21 19:12 ` John David Anglin
2003-09-21 19:16 ` Carlos O'Donell
2003-09-21 19:18 ` John David Anglin
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=20030919192813.GL18225@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=James.Bottomley@steeleye.com \
--cc=dave.anglin@nrc-cnrc.gc.ca \
--cc=dave@hiauly1.hia.nrc.ca \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.