On Wed, 29 Oct 2025 at 14:32, Frederick Virchanza Gotham via Std-Proposals <
std-proposals_at_[hidden]> wrote:

> On Wed, Oct 29, 2025 at 2:29 PM Ville Voutilainen wrote:
> >
> > > Then memcpy/memmove don't have special behavior, but you
> >> are also not to allowed to assume byte identity or copy/move manually.
> >
> > That's what we currently have. There are reasons why we have those
> > relocation functions, including that vtbl re-signing.
>
>
>
> But are we all in agreement that re-signing (or re-encrypting) a
> pointer is __not__ trivial ? And therefore, that all polymorphic
> object are __not__ trivially relocatable on arm64e?
>

Trivially relocatable does not mean the same thing as trivially copyable.