Re: libgcj/7587: direct threaded interpreter not thread-safe

Re: libgcj/7587: direct threaded interpreter not thread-safe

[Tom Tromey]

The following reply was made to PR libgcj/7587; it has been noted by GNATS.

From: Tom Tromey <tromey@redhat.com>
To: gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: libgcj/7587: direct threaded interpreter not thread-safe
Date: 13 Aug 2002 16:12:12 -0600

 Tom> The direct-threaded interpreter doesn't lock
 Tom> when testing or assigning `prepared'.
 Tom> This isn't thread-safe.
 
 This problem occurs in many places in the direct-threaded code :-(
 In particular it happens whenever we rewrite the compiled bytecode.
 
 Tom

libgcj/7587: direct threaded interpreter not thread-safe

[tromey]

>Number:         7587
>Category:       libgcj
>Synopsis:       direct threaded interpreter not thread-safe
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Aug 13 09:46:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Tom Tromey
>Release:        unknown-1.0
>Organization:
>Environment:

>Description:
The direct-threaded interpreter doesn't lock
when testing or assigning `prepared'.
This isn't thread-safe.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted: