Hi David,
> On 25 Jan 2024, at 10:16, Iain Sandoe wrote:
>
>> On 24 Jan 2024, at 18:31, David Malcolm wrote:
>>
>> On Tue, 2024-01-16 at 11:10 +, Iain Sandoe wrote:
>>> Tested on x86_64, i686 Darwin and x86_64 Linux,
>>> OK for trunk? when ?
>>> thanks,
>>> Iain
>>
>> Hi Iain, thanks for
Hi David,
> On 24 Jan 2024, at 18:31, David Malcolm wrote:
>
> On Tue, 2024-01-16 at 11:10 +, Iain Sandoe wrote:
>> Tested on x86_64, i686 Darwin and x86_64 Linux,
>> OK for trunk? when ?
>> thanks,
>> Iain
>
> Hi Iain, thanks for the patch.
>
> I'll have to defer to your Darwin expertise
On Tue, 2024-01-16 at 11:10 +, Iain Sandoe wrote:
> Tested on x86_64, i686 Darwin and x86_64 Linux,
> OK for trunk? when ?
> thanks,
> Iain
Hi Iain, thanks for the patch.
I'll have to defer to your Darwin expertise here; given that you've
tested it on the above configurations I'll assume it's
gentle ping,
this fixes quite a few of the new jit fails on darwin.
thanks
Iain
> On 16 Jan 2024, at 11:10, Iain Sandoe wrote:
>
> Tested on x86_64, i686 Darwin and x86_64 Linux,
> OK for trunk? when ?
> thanks,
> Iain
>
> --- 8< ---
>
> Currently, we have no exports list for libgccjit, which
Tested on x86_64, i686 Darwin and x86_64 Linux,
OK for trunk? when ?
thanks,
Iain
--- 8< ---
Currently, we have no exports list for libgccjit, which means that
all symbols are exported, including those from libstdc++ which is
linked statically into the lib. This causes failures when the
shared l