diff options
author | Rich Felker <dalias@aerifal.cx> | 2020-04-26 16:47:49 -0400 |
---|---|---|
committer | Rich Felker <dalias@aerifal.cx> | 2020-04-26 17:05:27 -0400 |
commit | 4486c579cbf0d989080705f515d08cb48636ba88 (patch) | |
tree | d457eee75de0bf937e262ce14f5792070cd7f6fa /src/string/strstr.c | |
parent | f3ecdc1043f44468b2db794b259c5f66737f6f84 (diff) | |
download | musl-4486c579cbf0d989080705f515d08cb48636ba88.tar.gz musl-4486c579cbf0d989080705f515d08cb48636ba88.tar.bz2 musl-4486c579cbf0d989080705f515d08cb48636ba88.tar.xz musl-4486c579cbf0d989080705f515d08cb48636ba88.zip |
remove arm (32-bit) support for vdso clock_gettime
it's been reported that the vdso clock_gettime64 function on (32-bit)
arm is broken, producing erratic results that grow at a rate far
greater than one reported second per actual elapsed second. the vdso
function seems to have been added sometime between linux 5.4 and 5.6,
so if there's ever been a working version, it was only present for a
very short window.
it's not clear what the eventual upstream kernel solution will be, but
something needs to be done on the libc side so as not to be producing
binaries that seem to work on older/existing/lts kernels (which lack
the function and thus lack the bug) but will break fantastically when
moving to newer kernels.
hopefully vdso support will be added back soon, but with a new symbol
name or version from the kernel to allow continued rejection of broken
ones.
Diffstat (limited to 'src/string/strstr.c')
0 files changed, 0 insertions, 0 deletions