Hi Ilya,
>> >> 2016-04-07 Rainer Orth <r...@cebitec.uni-bielefeld.de>
>> >>
>> >> * runtime/except-gcc.cpp (DEBUG_EXCEPTIONS): Allow redefinition.
>> >> * runtime/cilk_fiber.h (FIBER_DEBUG): Likewise.
>> >> * runtime/scheduler.h (REDPAR_DEBUG): Likewise.
>> > Ilya will have to chime in here -- we're a downstream consumer of the Cilk+
>> > runtime. So these patches need to go into Intel's tree first, then Ilya
>> > can bring them into the GCC tree.
>>
>> 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.
>
> Could you please submit your patch to
> <www.cilkplus.org/submit-cilk-contribution>?
> All patches for libcilkrts/* should go there first in order to avoid possible
> license issues, or possible losses during the merge.
sure, will do. So current upstream libcilkrts should easily
interoperate with current gcc trunk? That way, I'll be able to complete
the SPARC port from PR target/68945 upstream and just wait for the next
merge to drag it in.
Thanks.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
