Hello,

On 17/03/2025 10:03, Tomasz Kaminski wrote:
It seems that the patch is causing *first to be moved twice into the same position.

Good catch. I think I need to move it *back*, at least that's what __uninitialized_construct_buf_dispatch seems to do.

Given that we have constexpr allocations now, do we really need to avoid allocating temporary buffers, and using very slow implementation?

That's an option but I wanted to go there for GCC 16 (unless you greenlight me that this is doable right now).

I've written some more ruminations on this issue here:

https://forge.sourceware.org/gcc/gcc-TEST/pulls/44#issuecomment-792



PS: I've noticed that I have already accidentally bumped the FTM for constexpr stable sort; that's a bug as these two last algorithms were not inculded. I can decrement it for the time being, then rebump it again?


Thank you,
--
Giuseppe D'Angelo

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to