>>> On 10.02.17 at 12:44, wrote:
> It turns out that GCCs 4.9.2 and 6.3.0 instantiate __scanbit() in three
> translation units, but never references the result. All real uses of
> __scanbit() are already suitably inline.
While I'm not opposed to this at all, we should set ourselves a
reasonably
It turns out that GCCs 4.9.2 and 6.3.0 instantiate __scanbit() in three
translation units, but never references the result. All real uses of
__scanbit() are already suitably inline.
Signed-off-by: Andrew Cooper
---
CC: Jan Beulich
Forcing __scanbit() to be always_inline appears to cause GCC to
