about summary refs log tree commit diff
path: root/sysdeps/i386/i686/multiarch/rawmemchr-sse2.S
diff options
context:
space:
mode:
authorAdhemerval Zanella <adhemerval.zanella@linaro.org>2023-08-08 09:27:54 -0300
committerAdhemerval Zanella <adhemerval.zanella@linaro.org>2023-08-10 10:29:29 -0300
commit51cb52214fcd72849c640b12f5099ed3ac776181 (patch)
treea7ab22731c2b75d2c0cda48aa60ac093de6f2b54 /sysdeps/i386/i686/multiarch/rawmemchr-sse2.S
parentb163fca6c399808f6c447be98d09cd1165e78e07 (diff)
downloadglibc-51cb52214fcd72849c640b12f5099ed3ac776181.tar.gz
glibc-51cb52214fcd72849c640b12f5099ed3ac776181.tar.xz
glibc-51cb52214fcd72849c640b12f5099ed3ac776181.zip
x86_64: Fix build with --disable-multiarch (BZ 30721)
With multiarch disabled, the default memmove implementation provides
the fortify routines for memcpy, mempcpy, and memmove.  However, it
does not provide the internal hidden definitions used when building
with fortify enabled.  The memset has a similar issue.

Checked on x86_64-linux-gnu building with different options:
default and --disable-multi-arch plus default, --disable-default-pie,
--enable-fortify-source={2,3}, and --enable-fortify-source={2,3}
with --disable-default-pie.
Tested-by: Andreas K. Huettel <dilfridge@gentoo.org>
Reviewed-by: Siddhesh Poyarekar <siddhesh@sourceware.org>
Diffstat (limited to 'sysdeps/i386/i686/multiarch/rawmemchr-sse2.S')
0 files changed, 0 insertions, 0 deletions