public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/8995] race cases in interpreter
Date: Wed, 15 Mar 2006 17:17:00 -0000	[thread overview]
Message-ID: <20060315171728.19117.qmail@sourceware.org> (raw)
In-Reply-To: <bug-8995-360@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from tromey at gcc dot gnu dot org  2006-03-15 17:17 -------
Despite what the original report says, we don't really want to
resolve all entries when compiling.
Also it would be best to avoid any kind of synchronization at all.

One idea would be to 'or' the argument to one of these instructions
with 0x1 when the datum is unresolved.  This can be tested reasonably
quickly.  And, since these lookups are all idempotent, it does not
matter if two threads happen to do a small amount of redudant lookup
work.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=8995


       reply	other threads:[~2006-03-15 17:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-8995-360@http.gcc.gnu.org/bugzilla/>
2006-03-15 17:17 ` tromey at gcc dot gnu dot org [this message]
2008-08-22 16:18 ` aph at gcc dot gnu dot org
2008-08-22 16:20 ` aph at gcc dot gnu dot org
2008-08-22 16:58 ` aph at gcc dot gnu dot org
2008-09-23 13:52 ` aph at gcc dot gnu dot org
2008-12-27 14:45 ` pinskia at gcc dot gnu dot org
2009-02-05  9:42 ` aph at gcc dot gnu dot org
     [not found] <20021218141601.8995.tromey@gcc.gnu.org>
2005-05-03 23:17 ` tromey at gcc dot gnu dot org

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=20060315171728.19117.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@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).