On Sun, Jan 14, 2018 at 2:39 PM, David Woodhouse <[email protected]> wrote:
>
> I'm not convinced we want to do this, but I'll defer to Linus.
Well, I guess we have no choice, if gcc ends up using the stupid names.
And yes, apparently this just made our macros worse instead of
cleaning anything up. Oh well.
I do have one (possible) solution: just export both names. So you'd export
__x86_indirect_thunk_ax
__x86_indirect_thunk_rax
..
__x86_indirect_thunk_8
__x86_indirect_thunk_r8
as symbols (same code, obviously), and then
(a) the macros would be simpler
(b) it just happens to work with even the old gcc patch
But at this point I don't really care.
Linus
