This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH, MPX runtime 1/2] Integrate MPX runtime library
- From: Ilya Enkovich <enkovich dot gnu at gmail dot com>
- To: Jeff Law <law at redhat dot com>
- Cc: gcc-patches <gcc-patches at gcc dot gnu dot org>
- Date: Tue, 11 Nov 2014 23:22:20 +0300
- Subject: Re: [PATCH, MPX runtime 1/2] Integrate MPX runtime library
- Authentication-results: sourceware.org; auth=none
- References: <20141111153449 dot GB52080 at msticlxl57 dot ims dot intel dot com> <54626B4B dot 7030506 at redhat dot com>
2014-11-11 23:02 GMT+03:00 Jeff Law <law@redhat.com>:
> On 11/11/14 08:34, Ilya Enkovich wrote:
>>
>> Hi,
>>
>> This patch integrates MPX runtime library into GCC source tree. MPX
>> runtime is responsible for initialization of MPX feature in HW, signal
>> handling, reporting etc. Library is linked to codes compiled with -mmpx.
>>
>> Bootstrap is OK for x86_64-unknown-linux-gnu. OK for trunk?
>>
>> Thanks,
>> Ilya
>> --
>> 2014-11-11 Ilya Enkovich <ilya.enkovich@intel.com>
>>
>> * Makefile.def: Add libmpx.
>> * configure.ac: Add libmpx.
>> * Makefile.in: Regenerate.
>> * configure: Regenerate.
>>
>> gcc/
>>
>> 2014-11-11 Ilya Enkovich <ilya.enkovich@intel.com>
>>
>> * gcc.c (MPX_SPEC): New.
>> (LINK_COMMAND_SPEC): Add MPX_SPEC.
>
> Separate from Joseph's comments, is this library strictly a part of GCC, or
> is it shared with other implementations such as Clang/LLVM or ICC? If
> shared, which copy is the master? If shared, where should patches for the
> library be posted?
>
> I haven't looked closely, but what license is the actual runtime covered by?
> BSD-ish, LGPL, something else?
>
> Depending on the answers, we may need approval from the steering committee
> to accept. It's a process we've worked through for various other libraries
> (Cilk, Sanitizers, etc).
>
>
> Jeff
This library (some version of it) was only published in a binary form
some time ago. AFAIK currently it is not a part of any product.
Sources were never made public before. Sources go under the same
license as Cilk runtime and therefore require approval from steering
committee. Should I do something to start that process?
Thanks,
Ilya