From: "Boehm, Hans" <hans.boehm@hp.com>
To: "Andreas Tobler" <toa@pop.agri.ch>,
"Java Patches" <java-patches@gcc.gnu.org>
Subject: RE: [patch] PR30513
Date: Wed, 24 Jan 2007 23:06:00 -0000 [thread overview]
Message-ID: <BDA38860DCFD334EAEA905E44EE8E7EF6977C0@G3W0067.americas.hpqcorp.net> (raw)
In-Reply-To: <45B75202.2050600@pop.agri.ch>
Is there a spec of what these should do?
The patch, taken together with support on other architectures, is quite
inconsistent.
I would expect that the 32 and 64 bit variants would need the same kind
of fences.
It looks like x86-64 and i386 read_barrier is just broken, in that it
doesn't prevent compiler reordering.
I would have expected at least the PowerPC write barrier implementation
to use lwsync.
I'm probably biased, but it seems to me that the atomic_ops package
(used in gc7) is more coherent here.
Hans
> -----Original Message-----
> From: java-patches-owner@gcc.gnu.org
> [mailto:java-patches-owner@gcc.gnu.org] On Behalf Of Andreas Tobler
> Sent: Wednesday, January 24, 2007 4:33 AM
> To: Java Patches
> Subject: [patch] PR30513
>
> Hello all,
>
> for details have a look at the PR.
>
> Here comes my proposal for a patch. It is the easiest one in
> terms of testing and modifying files.
>
> Thanks goes to Tom and PinskiA.
>
> Ok for trunk?
>
> I'd like a sparc expert to look at the read/write barriers.
> Are they correct ? Who is one ??
>
>
> Andreas
>
> 2007-01-24 Andreas Tobler <a.tobler@schweiz.org>
>
> PR libgcj/30513
> * configure.host: Add forgottten sysdep_dir to sparc.
> Add a flag to
> libgcj_flags to undefine 'sun' at compile time.
> * sysdep/sparc/locks.h (read_barrier): New functions
> for 32 and 64 bit
> Sparc.
> (write_barrier): Likewise.
>
next prev parent reply other threads:[~2007-01-24 23:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 12:33 Andreas Tobler
2007-01-24 14:26 ` Andrew Haley
2007-01-24 23:06 ` Boehm, Hans [this message]
2007-01-25 5:29 ` Andreas Tobler
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=BDA38860DCFD334EAEA905E44EE8E7EF6977C0@G3W0067.americas.hpqcorp.net \
--to=hans.boehm@hp.com \
--cc=java-patches@gcc.gnu.org \
--cc=toa@pop.agri.ch \
/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).