[Bug target/84908] retpoline weirdness: 7.3.0-1 and 4.8.5-16: with -fPIC: R_X86_64_PC32 against undefined symbol `__x86_indirect_thunk_rax'

2018-08-15 Thread jason.vas.dias at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84908 --- Comment #14 from Jason Vas Dias --- RE: Comment #13: > You said that Andi Kleen had a comment. Can you point me to it? Here is a quote, from LKML message : Subject: Re: [PATCH v4.16-rc5 2/2] x86/vdso: \ VDSO should handle

[Bug target/84908] retpoline weirdness: 7.3.0-1 and 4.8.5-16: with -fPIC: R_X86_64_PC32 against undefined symbol `__x86_indirect_thunk_rax'

2018-08-14 Thread luto at kernel dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84908 --- Comment #13 from Andy Lutomirski --- I find this whole discussion very confusing. The problem has nothing to do with relocations AFAICT. The problem is that gcc is (as requested) generating retpolines, and it's set up to do it by calling

[Bug target/84908] retpoline weirdness: 7.3.0-1 and 4.8.5-16: with -fPIC: R_X86_64_PC32 against undefined symbol `__x86_indirect_thunk_rax'

2018-08-14 Thread jason.vas.dias at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84908 --- Comment #12 from Jason Vas Dias --- RE: Comment #11 : > notrace int _RETPOLINE_FUNC_ATTR_ > __vdso_clock_gettime(clockid_t clock, struct timespec *ts) should of course be notrace _RETPOLINE_FUNC_ATTR_ int

[Bug target/84908] retpoline weirdness: 7.3.0-1 and 4.8.5-16: with -fPIC: R_X86_64_PC32 against undefined symbol `__x86_indirect_thunk_rax'

2018-08-14 Thread jason.vas.dias at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84908 --- Comment #11 from Jason Vas Dias --- In reply to Comment #9 : Thanks Andy - I think it is because when the retpoline flags are enabled , the 'static inline' function calls in vclock_gettime.c have default function attributes which differ

[Bug target/84908] retpoline weirdness: 7.3.0-1 and 4.8.5-16: with -fPIC: R_X86_64_PC32 against undefined symbol `__x86_indirect_thunk_rax'

2018-08-14 Thread hjl.tools at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84908 --- Comment #10 from H.J. Lu --- (In reply to Andy Lutomirski from comment #9) > I haven't fully dug into this, but I do one one immediate question: why is > GCC generating a jump table for a five-entry switch statement if retpolines > are on?

[Bug target/84908] retpoline weirdness: 7.3.0-1 and 4.8.5-16: with -fPIC: R_X86_64_PC32 against undefined symbol `__x86_indirect_thunk_rax'

2018-08-14 Thread luto at kernel dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84908 Andy Lutomirski changed: What|Removed |Added CC||luto at kernel dot org --- Comment #9

[Bug target/84908] retpoline weirdness: 7.3.0-1 and 4.8.5-16: with -fPIC: R_X86_64_PC32 against undefined symbol `__x86_indirect_thunk_rax'

2018-03-19 Thread jason.vas.dias at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84908 --- Comment #8 from Jason Vas Dias --- Thanks for the clarification, and I hope the kernel developers stop compiling the mainline vDSO with -mindirect-branch=thunk-extern -mindirect-branch-register . But there are still a few things I am

[Bug target/84908] retpoline weirdness: 7.3.0-1 and 4.8.5-16: with -fPIC: R_X86_64_PC32 against undefined symbol `__x86_indirect_thunk_rax'

2018-03-19 Thread hjl.tools at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84908 H.J. Lu changed: What|Removed |Added Resolution|INVALID |MOVED --- Comment #7 from H.J. Lu --- It is

[Bug target/84908] retpoline weirdness: 7.3.0-1 and 4.8.5-16: with -fPIC: R_X86_64_PC32 against undefined symbol `__x86_indirect_thunk_rax'

2018-03-19 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84908 Richard Biener changed: What|Removed |Added Target||x86_64-*-*, i?86-*-*

[Bug target/84908] retpoline weirdness: 7.3.0-1 and 4.8.5-16: with -fPIC: R_X86_64_PC32 against undefined symbol `__x86_indirect_thunk_rax'

2018-03-16 Thread hjl.tools at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84908 --- Comment #5 from H.J. Lu --- (In reply to H.J. Lu from comment #3) > (In reply to Jason Vas Dias from comment #2) > > Thanks H.J. - > > > > RE: > > > vDSO isn't compiled with -mindirect-branch=thunk-extern in kernel > > > 4.16-rc5. Why

[Bug target/84908] retpoline weirdness: 7.3.0-1 and 4.8.5-16: with -fPIC: R_X86_64_PC32 against undefined symbol `__x86_indirect_thunk_rax'

2018-03-16 Thread hjl.tools at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84908 --- Comment #4 from H.J. Lu --- Created attachment 43685 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43685=edit Kernel patch for 4.16-rc5

[Bug target/84908] retpoline weirdness: 7.3.0-1 and 4.8.5-16: with -fPIC: R_X86_64_PC32 against undefined symbol `__x86_indirect_thunk_rax'

2018-03-16 Thread hjl.tools at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84908 --- Comment #3 from H.J. Lu --- (In reply to Jason Vas Dias from comment #2) > Thanks H.J. - > > RE: > > vDSO isn't compiled with -mindirect-branch=thunk-extern in kernel > > 4.16-rc5. Why isn't it the case for you? > > All I know is , when

[Bug target/84908] retpoline weirdness: 7.3.0-1 and 4.8.5-16: with -fPIC: R_X86_64_PC32 against undefined symbol `__x86_indirect_thunk_rax'

2018-03-16 Thread jason.vas.dias at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84908 --- Comment #2 from Jason Vas Dias --- Thanks H.J. - RE: > vDSO isn't compiled with -mindirect-branch=thunk-extern in kernel > 4.16-rc5. Why isn't it the case for you? All I know is , when submitting a patched vclock_gettime.c in which the

[Bug target/84908] retpoline weirdness: 7.3.0-1 and 4.8.5-16: with -fPIC: R_X86_64_PC32 against undefined symbol `__x86_indirect_thunk_rax'

2018-03-16 Thread hjl.tools at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84908 H.J. Lu changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|