[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#12541: Prefer plain 'static' to 'static inline'.
From: |
Eli Zaretskii |
Subject: |
bug#12541: Prefer plain 'static' to 'static inline'. |
Date: |
Sun, 30 Sep 2012 17:57:53 +0200 |
> From: Jason Rumney <jasonr@gnu.org>
> Cc: Paul Eggert <eggert@cs.ucla.edu>, 12541@debbugs.gnu.org
> Date: Sun, 30 Sep 2012 22:18:48 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > The inline functions in bidi.c _must_ be inlined for performance
> > reasons. If the only way to make sure they are is to make them
> > external, then so be it.
>
> The only way to ensure they are inlined is to make them macros. Modern
> compilers treat "inline" as a hint, not an instruction, if they take any
> notice of it at all.
In general, you are right. But I would settle with getting the right
result in practice. Surely, for GCC at least the information must be
there.