[Bug 256905] Missing clock_gettime VDSO on RISC-V
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 256905] Missing clock_gettime VDSO on RISC-V"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 256905] Missing clock_gettime VDSO on RISC-V"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 256905] Missing clock_gettime VDSO on RISC-V"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 256905] Missing clock_gettime VDSO on RISC-V"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 30 Jun 2021 14:30:23 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256905 Bug ID: 256905 Summary: Missing clock_gettime VDSO on RISC-V Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: riscv Assignee: riscv@FreeBSD.org Reporter: arichardson@FreeBSD.org I just ran truss on a Qt application and saw tons of clock_gettime syscalls. Looking at it in GDB shows that __vdso_clock_gettime returns ENOSYS. It appears that riscv_timer_timecount does not have a tc_fill_vdso_timehands function, so the tc_fill_vdso_timehands() function will always return 0. -- You are receiving this mail because: You are the assignee for the bug.