This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Allow redefinition of libcilkrts debug macros
- From: Rainer Orth <ro at CeBiTec dot Uni-Bielefeld dot DE>
- To: "Iyer\, Balaji V" <balaji dot v dot iyer at intel dot com>
- Cc: Jeff Law <law at redhat dot com>, "gcc-patches\ at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>, "Verbin\, Ilya" <ilya dot verbin at intel dot com>
- Date: Tue, 03 May 2016 14:05:50 +0200
- Subject: Re: Allow redefinition of libcilkrts debug macros
- Authentication-results: sourceware.org; auth=none
- References: <yddlh40a2kt dot fsf at lokon dot CeBiTec dot Uni-Bielefeld dot DE> <bad54655-5c0b-e6f2-88b8-6929665989d8 at redhat dot com> <yddoa8sx03y dot fsf at lokon dot CeBiTec dot Uni-Bielefeld dot DE> <BF230D13CA30DD48930C31D40993300047719B38 at fmsmsx101 dot amr dot corp dot intel dot com>
Hi Balaji,
> I suspected that much. It would be good to have a libcilkrts/README.gcc
> describing the rules which changes can go into the gcc tree directly, which
> need to go upstream first, and how. libo and libsanitizer already have
> this.
>
> Hi Rainer,
> It is mentioned under the "CONTRIBUTIONS" sections in the
> libcilkrts/README file :).
Sort of: it doesn't (and most likely shouldn't ) say anything about
if/when patches can first/exclusively go into the gcc tree.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University