From: "Boehm, Hans" <hans.boehm@hp.com>
To: Dave Korn <dave.korn.cygwin@gmail.com>, GCC Java <java@gcc.gnu.org>
Cc: Bryce McKinlay <bmckinlay@gmail.com>, Andrew Haley <aph@redhat.com>
Subject: RE: Usage of _Jv_AttachCurrentThread, _Jv_AttachCurrentThreadAsDaemon, _Jv_DetachCurrentThread.
Date: Thu, 11 Apr 2013 05:03:00 -0000 [thread overview]
Message-ID: <A3E67C2071F49C4CBC4F17E6D77CDDD2369C796F@G9W0725.americas.hpqcorp.net> (raw)
In-Reply-To: <5165F3EB.6080306@gmail.com>
> 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
prev parent reply other threads:[~2013-04-11 5:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 18:17 Dave Korn
2013-04-10 8:24 ` Andrew Haley
2013-04-10 9:34 ` Bryce McKinlay
2013-04-10 23:18 ` Dave Korn
2013-04-11 5:03 ` Boehm, Hans [this message]
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=A3E67C2071F49C4CBC4F17E6D77CDDD2369C796F@G9W0725.americas.hpqcorp.net \
--to=hans.boehm@hp.com \
--cc=aph@redhat.com \
--cc=bmckinlay@gmail.com \
--cc=dave.korn.cygwin@gmail.com \
--cc=java@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).