This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libgcj/8995] race cases in interpreter
- From: "tromey at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 15 Mar 2006 17:17:28 -0000
- Subject: [Bug libgcj/8995] race cases in interpreter
- References: <bug-8995-360@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- 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