On 3/23/25 8:28 AM, Iain Sandoe wrote:
Hi Jeff,
On 23 Mar 2025, at 14:25, Jeff Law wrote:
On 3/23/25 8:03 AM, Iain Sandoe wrote:
Tested on x86_64-Linux, Darwin,
OK for trunk?
backports?
thanks
Iain
--- 8< ---
Actually, the issue is not local to the libitm case, it currently affects
any 'cx
> On 23 Mar 2025, at 20:09, Jeff Law wrote:
>
>
>
> On 3/23/25 8:28 AM, Iain Sandoe wrote:
>> Hi Jeff,
>>> On 23 Mar 2025, at 14:25, Jeff Law wrote:
>>> On 3/23/25 8:03 AM, Iain Sandoe wrote:
Tested on x86_64-Linux, Darwin,
OK for trunk?
backports?
thanks
Iain
On 3/23/25 2:13 PM, Iain Sandoe wrote:
do you think it’s worth backporting (after some bake time)?
Feels pretty marginal to me, but I wouldn't object if you want to.
jeff
On 3/23/25 8:03 AM, Iain Sandoe wrote:
Tested on x86_64-Linux, Darwin,
OK for trunk?
backports?
thanks
Iain
--- 8< ---
Actually, the issue is not local to the libitm case, it currently affects
any 'cxx=true' top-level configured target library.
The issue is a missing export of CXX_FOR_TARGE
Hi Jeff,
> On 23 Mar 2025, at 14:25, Jeff Law wrote:
> On 3/23/25 8:03 AM, Iain Sandoe wrote:
>> Tested on x86_64-Linux, Darwin,
>> OK for trunk?
>> backports?
>> thanks
>> Iain
>> --- 8< ---
>> Actually, the issue is not local to the libitm case, it currently affects
>> any 'cxx=true' top-level
Tested on x86_64-Linux, Darwin,
OK for trunk?
backports?
thanks
Iain
--- 8< ---
Actually, the issue is not local to the libitm case, it currently affects
any 'cxx=true' top-level configured target library.
The issue is a missing export of CXX_FOR_TARGET.
PR libitm/88319
ChangeLog:
