From: Alan Modra <amodra@bigpond.net.au>
To: David Edelsohn <dje@watson.ibm.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: powerpc64 libstdc++
Date: Sun, 28 Jul 2002 05:40:00 -0000 [thread overview]
Message-ID: <20020728085458.GX26054@bubble.sa.bigpond.net.au> (raw)
In-Reply-To: <200207280020.UAA08484@makai.watson.ibm.com>
On Sat, Jul 27, 2002 at 08:20:30PM -0400, David Edelsohn wrote:
> >>>>> Alan Modra writes:
>
> Alan> I should have mentioned that I checked current glibc sources too. It's
> Alan> wrong to leave these functions in without some changes as they operate
> Alan> on "long", yet use "lwarx" and "stwcx.".
>
> Okay, remove the other functions.
>
> Somehow I think this would be nicer with _LOAD_LINKED and
> _STORE_CONDITONAL macros substituted in the inlined assembly and
> conditionally set to the appropriate PowerPC instruction.
http://www.gnu.org/prep/standards_11.html#SEC11 prefers "if ()" over
"#ifdef".
--
Alan Modra
IBM OzLabs - Linux Technology Centre
next prev parent reply other threads:[~2002-07-28 8:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-26 11:50 powerpc64 libffi not yet ported David Edelsohn
2002-07-26 12:40 ` Tom Tromey
2002-07-27 1:50 ` Alan Modra
2002-07-27 14:08 ` David Edelsohn
2002-07-27 3:45 ` powerpc64 libstdc++ Alan Modra
2002-07-27 14:33 ` David Edelsohn
2002-07-27 17:59 ` Alan Modra
2002-07-27 18:00 ` David Edelsohn
2002-07-28 5:40 ` Alan Modra [this message]
2002-07-28 13:06 ` David Edelsohn
2002-07-28 14:56 ` David Edelsohn
2002-07-28 16:27 ` dank
2002-07-28 22:31 ` Alan Modra
2002-07-29 1:00 ` David Edelsohn
2002-07-29 7:48 ` Daniel Jacobowitz
2002-07-29 8:16 ` David Edelsohn
2002-07-29 8:23 ` Daniel Jacobowitz
2002-07-29 20:34 ` dank
2002-07-29 21:32 ` David Edelsohn
2002-07-29 21:43 ` Daniel Jacobowitz
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=20020728085458.GX26054@bubble.sa.bigpond.net.au \
--to=amodra@bigpond.net.au \
--cc=dje@watson.ibm.com \
--cc=gcc-patches@gcc.gnu.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).