Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87v81sdfdi.fsf@oldenburg.str.redhat.com>
Date: Fri, 28 Jun 2024 21:41:29 +0200
From: Florian Weimer <fweimer@...hat.com>
To: Jonathan Wakely <jwakely.gcc@...il.com>
Cc: libc-coord@...ts.openwall.com,  enh <enh@...gle.com>,  Zijun Zhao
 <zijunzhao@...gle.com>
Subject: Re: aligned_realloc()

* Jonathan Wakely:

>> This would also be helpful in the implementation of data structures such
>> as std::vector, where in-place resizing and moving allocations require
>> different execution paths.
>
> Probably not, because std::vector goes through the C++ Allocator
> interface, which is very unlikely to expose something like this.

Does the default allocator have to call ::operator new(std::size_t)?
Is this an interposable interface, similar to malloc?

Thanks,
Florian

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.