public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: tromey@gcc.gnu.org
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: java/9254
Date: Tue, 28 Jan 2003 22:26:00 -0000	[thread overview]
Message-ID: <20030128222600.13575.qmail@sources.redhat.com> (raw)

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

From: tromey@gcc.gnu.org
To: gcc-gnats@gcc.gnu.org
Cc:  
Subject: java/9254
Date: 28 Jan 2003 22:23:36 -0000

 CVSROOT:	/cvs/gcc
 Module name:	gcc
 Changes by:	tromey@gcc.gnu.org	2003-01-28 22:23:36
 
 Modified files:
 	libjava        : ChangeLog win32-threads.cc 
 	libjava/include: win32-threads.h 
 
 Log message:
 	2003-01-28  Ranjit Mathew  <rmathew@hotmail.com>
 	
 	Fixes PR java/9254:
 	* include/win32-threads.h (_Jv_Mutex_t): Convert to a struct
 	additionally containing id of the owner thread as well as
 	the number of nested times the thread has acquired the mutex.
 	(_Jv_MutexInit): Initialise owner thread id and refcount to 0.
 	(_Jv_MutexDestroy): Reset owner thread id and refcount to 0.
 	(_Jv_MutexUnlock): Check if really the owner thread, reset
 	owner thread id to 0 before leaving, if leaving for the last
 	time.
 	(_Jv_MutexLock): Set owner thread id in the mutex and increment
 	refcount.
 	(_Jv_ThreadYield): Yield using a call to Sleep(0).
 	* win32-threads.cc (_Jv_CondWait): Check if really owner of
 	the passed mutex.
 	Pass handle of the broadcast event, instead of a pointer to it
 	in Win32 ResetEvent( ) call.
 	Remove incorrect return values.
 	(_Jv_CondDestroy): Close both event handles and delete
 	critical section.
 	(_Jv_CondNotify): Check if really the owner thread.
 	(_Jv_CondNotifyAll): Check if really the owner thread.
 	(_Jv_InitThreads): Change daemon_cond to a manual-reset event.
 	(really_start): Use SetEvent( ) to signal daemon_cond.
 	(_Jv_ThreadWait): Remove SignalObjectAndWait( ) and use
 	WaitForSingleObject( ) instead to wait for daemon_cond to be
 	signalled.
 
 Patches:
 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libjava/ChangeLog.diff?cvsroot=gcc&r1=1.1645&r2=1.1646
 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libjava/win32-threads.cc.diff?cvsroot=gcc&r1=1.8&r2=1.9
 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libjava/include/win32-threads.h.diff?cvsroot=gcc&r1=1.6&r2=1.7
 


             reply	other threads:[~2003-01-28 22:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-28 22:26 tromey [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-28 22:26 java/9254 tromey

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=20030128222600.13575.qmail@sources.redhat.com \
    --to=tromey@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).