Re: [PATCH] libstdc++: Reduce chances of object aliasing for function wrapper.

2025-08-26 Thread Jonathan Wakely
On Tue, 19 Aug 2025 at 16:12, Tomasz Kamiński wrote: > > Previously, an empty functor (EmptyIdFunc) stored inside a > std::move_only_function being first member of a Composite class could have the > same address as the base of the EmptyIdFunc type (see included test cases), > resulting in two obje

Re: [PATCH] libstdc++: Reduce chances of object aliasing for function wrapper.

2025-08-26 Thread Patrick Palka
On Tue, 19 Aug 2025, Tomasz Kamiński wrote: > Previously, an empty functor (EmptyIdFunc) stored inside a > std::move_only_function being first member of a Composite class could have the > same address as the base of the EmptyIdFunc type (see included test cases), > resulting in two objects of the

[PATCH] libstdc++: Reduce chances of object aliasing for function wrapper.

2025-08-19 Thread Tomasz Kamiński
Previously, an empty functor (EmptyIdFunc) stored inside a std::move_only_function being first member of a Composite class could have the same address as the base of the EmptyIdFunc type (see included test cases), resulting in two objects of the same type at the same address. This commit addresses