Messages in this thread | | | Date | Tue, 18 Sep 2007 09:58:14 -0700 | From | "Ulrich Drepper" <> | Subject | Re: x86_64: vsyscall vs vdso |
| |
On 9/17/07, Francis Moreau <francis.moro@gmail.com> wrote: > Actually if we could easily retrieve the vdso in a process memory > mapping (through a new syscall or /proc/self/maps), it should be easy > for gcc/ld to statically links vdso functions into a statically linked > app, shouldn't it ?
Nonsense. All the code which is in the vdso has a real implementation in libc. No need to substitute. The vdso is only there to adjust a program to the actual environment in which it is executed and not in which it is built. Your suggestion would do the latter which is complete and utter nonsense. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |