From: Daniel Jacobowitz <drow@false.org>
To: Brad Midgley <brad@pht.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: test & set ppc assembly (libgcj vs. threads)
Date: Mon, 2 Aug 1999 14:49:45 -0400 [thread overview]
Message-ID: <19990802144945.A28429@them.org> (raw)
In-Reply-To: <Pine.LNX.3.95.990802095050.20647A-100000@pacific.pht.com>; from Brad Midgley on Mon, Aug 02, 1999 at 09:54:55AM -0600
On Mon, Aug 02, 1999 at 09:54:55AM -0600, Brad Midgley wrote:
>
> hi...
>
> i would like to see libgcj work on ppc. i guess there isn't anyone working
> on it because there is missing stuff even in the cvs version.
>
> could one of you ppc assembly gurus put forward the code to do a test &
> set? the header here hopefully provides all the necessary context with
> the x86 and alpha implementations...
Look at the debian package of libgc4. We patched this a while ago.
The patch is in the .diff.gz on any debian source mirror (<searches>):
/debian/dists/unstable/main/source/libs/libgc4_*
Dan
/--------------------------------\ /--------------------------------\
| Daniel Jacobowitz |__| SCS Class of 2002 |
| Debian GNU/Linux Developer __ Carnegie Mellon University |
| dan@debian.org | | dmj+@andrew.cmu.edu |
\--------------------------------/ \--------------------------------/
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-08-02 18:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-02 15:54 test & set ppc assembly (libgcj vs. threads) Brad Midgley
1999-08-02 18:49 ` Daniel Jacobowitz [this message]
1999-08-02 19:02 ` David Edelsohn
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=19990802144945.A28429@them.org \
--to=drow@false.org \
--cc=brad@pht.com \
--cc=linuxppc-dev@lists.linuxppc.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 NNTP newsgroup(s).