public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aph at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug java/12755] Binary Compatibility: Resolving static methods and classes is not thread safe Date: Thu, 23 Sep 2004 09:09:00 -0000 [thread overview] Message-ID: <20040923090913.29118.qmail@sourceware.org> (raw) In-Reply-To: <20031024131706.12755.aph@gcc.gnu.org> ------- Additional Comments From aph at gcc dot gnu dot org 2004-09-23 09:09 ------- It's more or less impossible to test. In short, we need to make sure that resolution of indirect dispatch tables is correctly locked so that it's impossible for double resolution to occur. If resolution is now within a class mutex, this bug may be closed. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12755
next prev parent reply other threads:[~2004-09-23 9:09 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-10-24 13:17 [Bug java/12755] New: " aph at gcc dot gnu dot org 2003-10-24 13:21 ` [Bug java/12755] " aph at gcc dot gnu dot org 2003-10-24 13:25 ` aph at gcc dot gnu dot org 2003-10-24 16:48 ` pinskia at gcc dot gnu dot org 2003-12-19 19:30 ` aph at gcc dot gnu dot org 2003-12-19 20:08 ` aph at gcc dot gnu dot org 2004-01-09 17:09 ` cvs-commit at gcc dot gnu dot org 2004-01-17 8:35 ` dhazeghi at yahoo dot com 2004-01-17 11:31 ` aph at gcc dot gnu dot org 2004-03-16 16:25 ` pinskia at gcc dot gnu dot org 2004-05-06 15:52 ` aph at gcc dot gnu dot org 2004-05-26 22:38 ` pinskia at gcc dot gnu dot org 2004-09-20 22:27 ` tromey at gcc dot gnu dot org 2004-09-20 23:24 ` tromey at gcc dot gnu dot org 2004-09-23 9:09 ` aph at gcc dot gnu dot org [this message] 2004-09-23 16:53 ` tromey at gcc dot gnu dot org 2004-12-01 3:09 ` pinskia 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=20040923090913.29118.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).