This is the mail archive of the java-patches@gcc.gnu.org mailing list for the Java project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: PATCH: Support threads on FreeBSD/i386



Loren> 2001-08-20  Loren J. Rittle  <ljrittle@acm.org>
Loren> * configure.in (GC_FREEBSD_THREADS): Define it instead of...
Loren> (FREEBSD_THREADS): ...this to follow the latest macro convention.
Loren> * configure: Rebuilt.

Loren> * dyn_load.c: While basically copying the minimal
Loren> LINUX_THREADS code path, enable pthread support on FreeBSD.
Loren> * gc_dlopen.c: Likewise.
Loren> * misc.c: Likewise.
Loren> * os_dep.c: Likewise.
Loren> * threadlibs.c: Likewise.
Loren> * include/gc.h: Likewise.
Loren> * include/gc_pthread_redirects.h: Likewise.
Loren> * include/private/gc_locks.h: Likewise.
Loren> * include/private/gc_priv.h: Likewise.
Loren> * tests/test.c: Likewise.
Loren> * include/private/gcconfig.h: Likewise.
Loren> (MPROTECT_VDB): Do not define when GC_FREEBSD_THREADS.
Loren> * linux_threads.c: Likewise.
Loren> (WRAP_FUNC(pthread_join)): Fix-up spurious EINTR return from
Loren> REAL_FUNC(pthread_join) in the wrapper.

> Some of the code seems to use FREEBSD_THREADS and some uses
> GC_FREEBSD_THREADS.  Why not just use the latter everywhere?

Would you believe that I attempted to follow the convention in use
near any particular change...

I will gladly update to use GC_FREEBSD_THREADS everywhere and remove
all trace of FREEBSD_THREADS.  Either way, I will wait until Hans can
comment.

Given that I still haven't figured out the random hang (I have only
spent an hour), I am actually concerned to install this patch.  On the
light side, I can now report that I have never seen it hang a real
libjava program.

Regards,
Loren


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]