Skip to contentSkip to conversation

kill __always_inline

PATCH Andi Kleen 1 participant 1 message Sep 1, 2004 4 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

Andi Kleen

author
#4 lore raw
Quoted 6 lines · Nigel Cunningham

Excuse me if I'm being ignorant, but I thought always_inline was introduced because with some recent versions of gcc, inline wasn't doing the job (suspend2, which requires a working inline, was broken by it for example). That is to say, doesn't the definition of always_inline vary with the compiler version?

It is just inline on some old gcc versions that didn't have __attribute__((always_inline)). But on these plain inline is usually fine
- it will just inline. Only later versions of gcc broke their inlining algorithm, but they luckily added this attribute as a workaround.

When you have functions that require inlining always mark them __always_inline

-Andi