RE: Usage of _Jv_AttachCurrentThread, _Jv_AttachCurrentThreadAsDaemon, _Jv_DetachCurrentThread.

>   Upstream now includes a new support library, libatomic_ops, that is
> licensed under a combination of GPLv2 and a custom "MIT-style" licence.  Is
> that likely to be any problem?
> 
libatomic_ops turns out to have mostly been a useful evolutionary step on the way to C11/C++11 atomics.  If this is an issue, it should now be fairly easy, at least in the context of a recent gcc, to replace it with the latter.

The licensing was intended not to be a problem.  The GPLv2 pieces are either higher-level pieces not be needed at all by gcc, or are only tests for the library.  The atomics library itself is covered by the MIT-style license.  But, as I said, I think it's no longer critical.

Hans