[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: inline build_string performance
From: |
Paul Eggert |
Subject: |
Re: inline build_string performance |
Date: |
Tue, 26 Jun 2012 09:42:57 -0700 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 |
On 06/26/2012 09:29 AM, Dmitry Antipov wrote:
>
> The core idea of this stuff is to eliminate calls to strlen when an
> argument of build_string is a compile-time constant
That sounds worthwhile for critical paths.
How about reverting the build_string change, and defining a new
inline function build_literal intended for when the argument is a
string literal and for when speed is more important than conserving
code space? That would give us speed where speed matters and where
we know it'll be faster, while avoiding code bloat otherwise.
build_string and build_literal would have identical semantics,
but different performance properties.
- inline build_string performance, Paul Eggert, 2012/06/26
- Re: inline build_string performance, Andreas Schwab, 2012/06/26
- Re: inline build_string performance, Dmitry Antipov, 2012/06/26
- Re: inline build_string performance,
Paul Eggert <=
- Re: inline build_string performance, Dmitry Antipov, 2012/06/26
- Re: inline build_string performance, Paul Eggert, 2012/06/26
- Re: inline build_string performance, Dmitry Antipov, 2012/06/26
- Re: inline build_string performance, Paul Eggert, 2012/06/26
- Re: inline build_string performance, Eli Zaretskii, 2012/06/26
- Re: inline build_string performance, Thien-Thi Nguyen, 2012/06/26
Re: inline build_string performance, Stefan Monnier, 2012/06/26