On 21/08/2023 23:26, Jonathan Wakely wrote:
On Mon, 21 Aug 2023 at 21:20, François Dumont wrote:
Here is the updated and tested patch.
OK for trunk, thanks.
We could consider it for the branches too (I'm going to remove the
global strings on the gcc-13 branch tomorrow).
It's not fixing an
On Mon, 21 Aug 2023 at 21:20, François Dumont wrote:
>
> Here is the updated and tested patch.
OK for trunk, thanks.
We could consider it for the branches too (I'm going to remove the
global strings on the gcc-13 branch tomorrow).
>
> On 21/08/2023 20:07, Jonathan Wakely wrote:
> > On Mon, 21
Here is the updated and tested patch.
On 21/08/2023 20:07, Jonathan Wakely wrote:
On Mon, 21 Aug 2023 at 18:05, François Dumont via Libstdc++
wrote:
Hi
Here is a propocal to fix tests sensitive to libstdc++ internal allocations.
Surely the enter() and exit() calls should be a constructor and
On Mon, 21 Aug 2023 at 18:05, François Dumont via Libstdc++
wrote:
>
> Hi
>
> Here is a propocal to fix tests sensitive to libstdc++ internal allocations.
Surely the enter() and exit() calls should be a constructor and destructor?
The constructor could use count() to get the count, and then rest
Hi
Here is a propocal to fix tests sensitive to libstdc++ internal allocations.
Tested by restoring allocation in tzdb.cc.
As announced I'm also adding a test to detect such allocations. If it is
ok let me know if you prefer to see it in a different place.
libstdc++: Fix tests relying on
