Re: Fix gnu versioned namespace mode 00/03

["François Dumont" <frs.dumont@gmail.com>]

On 07/05/2024 18:15, Iain Sandoe wrote:
> Hi François
>
>> On 4 May 2024, at 22:11, François Dumont <frs.dumont@gmail.com> wrote:
>>
>> Here is the list of patches to restore gnu versioned namespace mode.
>>
>> 1/3: Bump gnu version namespace
>>
>> This is important to be done first so that once build of gnu versioned namespace is fixed there is no chance to have another build of '__8' version with a different abi than last successful '__8' build.
>>
>> 2/3: Fix build using cxx11 abi for versioned namespace
>>
>> 3/3: Proposal to default to "new" abi when dual abi is disabled and accept any default-libstdcxx-abi either dual abi is enabled or not.
>>
>> All testsuite run for following configs:
>>
>> - dual abi
>>
>> - gcc4-compatible only abi
>>
>> - new only abi
>>
>> - versioned namespace abi
> At the risk of delaying this (a bit) - I think we should also consider items like once_call that have broken impls.
Do you have any pointer to this once_call problem, sorry I'm not aware 
about it (apart from your messages).
>   in the current library - and at least get proposed replacements available behind the versioned namespace; rather than using up a namespace version with the current broken code.

I'm not proposing to fix all library bugs on all platforms with this 
patch, just fix the versioned namespace mode.

As to do so I also need to adopt cxx11 abi in versioned mode it already 
justify a bump of version.

>
> I have a proposed once_call replacement (but I think Jonathan also has one or more alternatives there)
>
> Please can we try to identify any other similar blocked fixes?

How ? We can only count on bugzilla bug reports to do so, no ?

If we face another similar problem in the future, after gcc 15 release, 
then we'll just have to bump again. Is it such a problem ?

The reason I'm proposing to integrate this patch this early in gcc 15 
stage is to have time to integrate any other library fix/optimization 
that could make use of it. I already have 1 on my side for the hashtable 
implementation. I hope your once_call fix also have time to be ready for 
gcc 15, no ?

François