This is the mail archive of the
mailing list for the GCC project.
Re: implementation & optimization of std::function with and without allocator
- From: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- To: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Cc: Basile Starynkevitch <basile at starynkevitch dot net>
- Date: Sat, 25 Jan 2014 23:45:19 +0000
- Subject: Re: implementation & optimization of std::function with and without allocator
- Authentication-results: sourceware.org; auth=none
- References: <1390665655 dot 18254 dot 19 dot camel at glinka dot lesours> <CAH6eHdSAiMQo4Su+K0q00nex2QHTEcg=_J6kLCbvZ1=2JNqjjQ at mail dot gmail dot com> <alpine dot DEB dot 2 dot 10 dot 1401260019020 dot 3743 at laptop-mg dot saclay dot inria dot fr>
On 25 January 2014 23:40, Marc Glisse wrote:
> On Sat, 25 Jan 2014, Jonathan Wakely wrote:
>> That isn't similar and the use of std::array is irrelevant.
>> std::function involves type erasure, usually dynamic allocation, and
>> indirection through function pointers. If you don't use std::function
>> then none of that needs to be optimised away.
> Indeed. But optimizing the code generated when std::function is used seems a
> worthy goal to me.
Yes, I'd love to see it done, I'm just not surprised that it isn't