aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2021-08-27Fix blocking pthread_join. [BZ #23137]Stefan Liebler2-5/+14
On s390 (31bit) if glibc is build with -Os, pthread_join sometimes blocks indefinitely. This is e.g. observable with testcase intl/tst-gettext6. pthread_join is calling lll_wait_tid(tid), which performs the futex-wait syscall in a loop as long as tid != 0 (thread is alive). On s390 (and build with -Os), tid is loaded from memory before comparing against zero and then the tid is loaded a second time in order to pass it to the futex-wait-syscall. If the thread exits in between, then the futex-wait-syscall is called with the value zero and it waits until a futex-wake occurs. As the thread is already exited, there won't be a futex-wake. In lll_wait_tid, the tid is stored to the local variable __tid, which is then used as argument for the futex-wait-syscall. But unfortunately the compiler is allowed to reload the value from memory. With this patch, the tid is loaded with atomic_load_acquire. Then the compiler is not allowed to reload the value for __tid from memory. ChangeLog: [BZ #23137] * sysdeps/nptl/lowlevellock.h (lll_wait_tid): Use atomic_load_acquire to load __tid. (cherry picked from commit 1660901840dfc9fde6c5720a32f901af6f08f00a)
2021-08-27Add PTRACE_SECCOMP_GET_METADATA from Linux 4.16 to sys/ptrace.h.Joseph Myers11-8/+76
This patch adds the PTRACE_SECCOMP_GET_METADATA constant from Linux 4.16 to all relevant sys/ptrace.h files. A type struct __ptrace_seccomp_metadata, analogous to other such types, is also added. Tested for x86_64, and with build-many-glibcs.py. * sysdeps/unix/sysv/linux/sys/ptrace.h (PTRACE_SECCOMP_GET_METADATA): New enum value and macro. * sysdeps/unix/sysv/linux/bits/ptrace-shared.h (struct __ptrace_seccomp_metadata): New type. * sysdeps/unix/sysv/linux/aarch64/sys/ptrace.h (PTRACE_SECCOMP_GET_METADATA): Likewise. * sysdeps/unix/sysv/linux/arm/sys/ptrace.h (PTRACE_SECCOMP_GET_METADATA): Likewise. * sysdeps/unix/sysv/linux/ia64/sys/ptrace.h (PTRACE_SECCOMP_GET_METADATA): Likewise. * sysdeps/unix/sysv/linux/powerpc/sys/ptrace.h (PTRACE_SECCOMP_GET_METADATA): Likewise. * sysdeps/unix/sysv/linux/s390/sys/ptrace.h (PTRACE_SECCOMP_GET_METADATA): Likewise. * sysdeps/unix/sysv/linux/sparc/sys/ptrace.h (PTRACE_SECCOMP_GET_METADATA): Likewise. * sysdeps/unix/sysv/linux/tile/sys/ptrace.h (PTRACE_SECCOMP_GET_METADATA): Likewise. * sysdeps/unix/sysv/linux/x86/sys/ptrace.h (PTRACE_SECCOMP_GET_METADATA): Likewise. (cherry picked from commit 9320ca88a197d3620d3553ccc2d9402d981d7e23)
2021-08-27resolv: Fully initialize struct mmsghdr in send_dg [BZ #23037]Florian Weimer2-19/+27
(cherry picked from commit 583a27d525ae189bdfaa6784021b92a9a1dae12e)
2021-08-27manual: Various fixes to the mbstouwcs example, and mbrtowc updateFlorian Weimer3-43/+92
The example did not work because the null byte was not converted, and mbrtowc was called with a zero-length input string. This results in a (size_t) -2 return value, so the function always returns NULL. The size computation for the heap allocation of the result was incorrect because it did not deal with integer overflow. Error checking was missing, and the allocated memory was not freed on error paths. All error returns now set errno. (Note that there is an assumption that free does not clobber errno.) The slightly unportable comparision against (size_t) -2 to catch both (size_t) -1 and (size_t) -2 return values is gone as well. A null wide character needs to be stored in the result explicitly, to terminate it. The description in the manual is updated to deal with these finer points. The (size_t) -2 behavior (consuming the input bytes) matches what is specified in ISO C11. (cherry picked from commit cf138b0c83b3210990b29772e2af5982fb0e3c26) (cherry picked from commit 690c3475f1417c99cb0fc69f35d77560c24c1d69)
2021-08-27manual: Move mbstouwcs to an example C fileFlorian Weimer3-22/+34
(cherry picked from commit 0f339252697e6dcfc9e00be6cd8272d4260b90d2)
2021-08-27Update RWF_SUPPORTED for Linux kernel 4.16 [BZ #22947]H.J. Lu5-1/+19
Add RWF_APPEND to RWF_SUPPORTED to support Linux kernel 4.16. [BZ #22947] * bits/uio-ext.h (RWF_APPEND): New. * sysdeps/unix/sysv/linux/bits/uio-ext.h (RWF_APPEND): Likewise. * manual/llio.texi: Document RWF_APPEND. * misc/tst-preadvwritev2-common.c (RWF_APPEND): New. (RWF_SUPPORTED): Add RWF_APPEND. (cherry picked from commit f2652643d7234c08205b75f527191c2e2b35251f)
2021-08-27getlogin_r: return early when linux sentinel value is setJesse Hathaway2-0/+14
When there is no login uid Linux sets /proc/self/loginid to the sentinel value of, (uid_t) -1. If this is set we can return early and avoid needlessly looking up the sentinel value in any configured nss databases. Checked on aarch64-linux-gnu. * sysdeps/unix/sysv/linux/getlogin_r.c (__getlogin_r_loginuid): Return early when linux sentinel value is set. Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org> (cherry picked from commit cc8a1620eb97ccddd337d157263c13c57b39ab71)
2021-08-27Fix crash in resolver on memory allocation failure (bug 23005)Andreas Schwab2-0/+11
(cherry picked from commit f178e59fa5eefbbd37fde040ae8334aa5c857ee1)
2021-08-27Fix signed integer overflow in random_r (bug 17343).Joseph Myers2-5/+10
Bug 17343 reports that stdlib/random_r.c has code with undefined behavior because of signed integer overflow on int32_t. This patch changes the code so that the possibly overflowing computations use unsigned arithmetic instead. Note that the bug report refers to "Most code" in that file. The places changed in this patch are the only ones I found where I think such overflow can occur. Tested for x86_64 and x86. [BZ #17343] * stdlib/random_r.c (__random_r): Use unsigned arithmetic for possibly overflowing computations. (cherry picked from commit 8a07b0c43c46a480da070efd53a2720195e2256f)
2021-08-27Add tst-sigaction.c to test BZ #23069Aurelien Jarno3-1/+62
This simple test uses sigaction to define a signal handler. It then uses sigaction again to fetch the information about the same signal handler, and check that they are consistent. This is enough to detect mismatches between struct kernel_sigaction and the kernel version of struct sigaction, like in BZ #23069. Changelog: * signal/tst-sigaction.c: New file to test BZ #23069. * signal/Makefile (tests): Fix indentation. Add tst-sigaction. (cherry picked from commit 7a6f74787132aca8e3809cae8d9e7bc7bfd55ce1)
2021-08-27RISC-V: fix struct kernel_sigaction to match the kernel version [BZ #23069]Aurelien Jarno2-0/+12
The RISC-V kernel doesn't define SA_RESTORER, hence the kernel version of struct sigaction doesn't have the sa_restorer field. The default kernel_sigaction.h therefore can't be used. This patch adds a RISC-V specific version of kernel_sigaction.h to fix the issue. This fixes for example the libnih testsuite. Note that this patch is not needed in master as the bug has been fixed by commit b4a5d26d8835 ("linux: Consolidate sigaction implementation").
2021-08-27Linux i386: tst-bz21269 triggers SIGBUS on some kernelsFlorian Weimer2-0/+7
In addition to SIGSEGV and SIGILL, SIGBUS is also a possible signal generated by the kernel. (cherry picked from commit 4d76d3e59d31aa690f148fc0c95cc0c581aed3e8)
2021-08-27Fix i386 memmove issue (bug 22644).Andrew Senkevich3-6/+72
[BZ #22644] * sysdeps/i386/i686/multiarch/memcpy-sse2-unaligned.S: Fixed branch conditions. * string/test-memmove.c (do_test2): New testcase. (cherry picked from commit cd66c0e584c6d692bc8347b5e72723d02b8a8ada)
2021-08-27Update ChangeLog for BZ 22884 - riscv fmax/fminDJ Delorie1-0/+1
(cherry picked from commit 7e04eb2932d3126c721ee2bc0d664a5bbea2f41f)
2021-08-27RISC-V: fmax/fmin: Handle signalling NaNs correctly.Andrew Waterman5-8/+43
RISC-V's fmax(sNAN,4) returns 4 but glibc expects it to return qNAN. * sysdeps/riscv/rvd/s_fmax.c (__fmax): Handle sNaNs correctly. * sysdeps/riscv/rvd/s_fmin.c (__fmin): Likewise. * sysdeps/riscv/rvf/s_fmaxf.c (__fmaxf): Likewise. * sysdeps/riscv/rvf/s_fminf.c (__fminf): Likewise. (cherry picked from commit fdcc625376505eacb1125a6aeba57501407a30ec)
2021-08-27RISC-V: Do not initialize $gp in TLS macros.DJ Delorie2-17/+7
RISC-V TLS doesn't require GP to be initialized, and doing so breaks TLS in a shared object. (cherry picked from commit 8090720a87e42fddc31396f6126112d4b8014d8e)
2021-08-27NEWS: Add entries for bugs: 22848, 22932, 22937, 22963.Rafal Luzynski1-0/+10
Alternative (nominative/genitive) month names have been added to the Catalan and Czech locale data and the abbreviated alternative names to Catalan and Greek. (cherry picked from commit c553cd6f7e939ae4ef62b52b3c55fbe76dddecee)
2021-08-27cs_CZ locale: Add alternative month names (bug 22963).Rafal Luzynski2-1/+21
Add alternative month names, primary month names are genitive now. [BZ #22963] * localedata/locales/cs_CZ (mon): Rename to... (alt_mon): This. (mon): Import from CLDR (genitive case). Reviewed-by: Carlos O'Donell <carlos@redhat.com> (cherry picked from commit 807fee29d2c967e24e3fe05e2182ba53e96e9178)
2021-08-27Greek (el_CY, el_GR) locales: Introduce ab_alt_mon (bug 22937).Rafal Luzynski3-2/+24
As spotted by GNOME translation team, Greek language has the actually visible difference between the abbreviated nominative and the abbreviated genitive case for some month names. Examples: and more month names with similar differences. Original discussion: https://bugzilla.gnome.org/show_bug.cgi?id=793645#c21 [BZ #22937] * localedata/locales/el_CY (abmon): Rename to... (ab_alt_mon): This. (abmon): Import from CLDR (abbreviated genitive case). * localedata/locales/el_GR (abmon): Rename to... (ab_alt_mon): This. (abmon): Import from CLDR (abbreviated genitive case). Reviewed-by: Carlos O'Donell <carlos@redhat.com> (cherry picked from commit e7155a28ef61f240da156e1cea410b61afca14ad)
2018-03-08lt_LT locale: Update abbreviated month names (bug 22932).Rafal Luzynski2-6/+11
A GNOME translator asked to use the same abbreviated month names as provided by CLDR. This sounds reasonable. See the discussion: https://bugzilla.gnome.org/show_bug.cgi?id=793645#c27 [BZ #22932] * localedata/locales/lt_LT (abmon): Synchronize with CLDR. Reviewed-by: Carlos O'Donell <carlos@redhat.com> (cherry picked from commit 71d7b121686f6d91cd5a630dcfb72197b5d8284a)
2018-03-06ca_ES locale: Update LC_TIME (bug 22848).Robert Buj2-40/+91
Add/fix alternative month names, long & short formats, am_pm, abday settings, and improve indentation for Catalan. [BZ #22848] * localedata/locales/ca_ES (abmon): Rename to... (ab_alt_mon): This, then synchronize with CLDR (nominative case). (mon): Rename to... (alt_mon): This. (abmon): Import from CLDR (genitive case, month names preceded by "de" or "d'"). (mon): Likewise. (abday): Synchronize with CLDR. (d_t_fmt): Likewise. (d_fmt): Likewise. (am_pm): Likewise. (LC_TIME): Improve indentation. (LC_TELEPHONE): Likewise. (LC_NAME): Likewise. (LC_ADDRESS): Likewise. Reviewed-by: Carlos O'Donell <carlos@redhat.com> (cherry picked from commit a00bffe8b531693d3b26c1e87afe4b9eac84474c)
2018-03-12Update translations from the Translation ProjectDmitry V. Levin2-3132/+6066
* po/pt_BR.po: Update translations. (cherry picked from commit 778f1974863d63e858b6d0105e41d6f0c30732d3)
2017-11-17i386: Fix i386 sigaction sa_restorer initialization (BZ#21269)Adhemerval Zanella5-1/+247
This patch fixes the i386 sa_restorer field initialization for sigaction syscall for kernel with vDSO. As described in bug report, i386 Linux (and compat on x86_64) interprets SA_RESTORER clear with nonzero sa_restorer as a request for stack switching if the SS segment is 'funny'. This means that anything that tries to mix glibc's signal handling with segmentation (for instance through modify_ldt syscall) is randomly broken depending on what values lands in sa_restorer. The testcase added is based on Linux test tools/testing/selftests/x86/ldt_gdt.c, more specifically in do_multicpu_tests function. The main changes are: - C11 atomics instead of plain access. - Remove x86_64 support which simplifies the syscall handling and fallbacks. - Replicate only the test required to trigger the issue. Checked on i686-linux-gnu. [BZ #21269] * sysdeps/unix/sysv/linux/i386/Makefile (tests): Add tst-bz21269. * sysdeps/unix/sysv/linux/i386/sigaction.c (SET_SA_RESTORER): Clear sa_restorer for vDSO case. * sysdeps/unix/sysv/linux/i386/tst-bz21269.c: New file. (cherry picked from commit 68448be208ee06e76665918b37b0a57e3e00c8b4)
2018-03-02Fix multiple definitions of __nss_*_database (bug 22918)Andreas Schwab8-5/+22
(cherry picked from commit eaf6753f8aac33a36deb98c1031d1bad7b593d2d)
2018-03-01[BZ #22342] Fix netgroup cache keys.DJ Delorie3-1/+8
Unlike other nscd caches, the netgroup cache contains two types of records - those for "iterate through a netgroup" (i.e. setnetgrent()) and those for "is this user in this netgroup" (i.e. innetgr()), i.e. full and partial records. The timeout code assumes these records have the same key for the group name, so that the collection of records that is "this netgroup" can be expired as a unit. However, the keys are not the same, as the in-netgroup key is generated by nscd rather than being passed to it from elsewhere, and is generated without the trailing NUL. All other keys have the trailing NUL, and as noted in the linked BZ, debug statements confirm that two keys for the same netgroup are added to the cache with two different lengths. The result of this is that as records in the cache expire, the purge code only cleans out one of the two types of entries, resulting in stale, possibly incorrect, and possibly inconsistent cache data. The patch simply includes the existing NUL in the computation for the key length ('key' points to the char after the NUL, and 'group' to the first char of the group, so 'key-group' includes the first char to the NUL, inclusive). [BZ #22342] * nscd/netgroupcache.c (addinnetgrX): Include trailing NUL in key value. Reviewed-by: Carlos O'Donell <carlos@redhat.com> (cherry picked from commit 1c81d55fc4b07b51adf68558ba74ce975153e580)
2018-02-10linux/powerpc: sync sys/ptrace.h with Linux 4.15 [BZ #22433, #22807]Dmitry V. Levin3-0/+74
Tested with strace. * sysdeps/unix/sysv/linux/powerpc/sys/ptrace.h (__ptrace_request): Add PTRACE_GETREGS, PTRACE_SETREGS, PTRACE_GETFPREGS, PTRACE_SETFPREGS, PTRACE_GETVRREGS, PTRACE_SETVRREGS, PTRACE_GETEVRREGS, PTRACE_SETEVRREGS, PTRACE_GETREGS64, PTRACE_SETREGS64, PTRACE_GET_DEBUGREG, PTRACE_SET_DEBUGREG, PTRACE_GETVSRREGS, PTRACE_SETVSRREGS, and PTRACE_SINGLEBLOCK. (cherry picked from commit f5f473a9d0e8fdbede858fa1ef0d01d12142367b)
2018-02-26powerpc: Undefine Linux ptrace macros that conflict with __ptrace_requestTulio Magno Quites Machado Filho2-0/+48
Linux ptrace headers define macros whose tokens conflict with the constants of enum __ptrace_request causing build errors when asm/ptrace.h or linux/ptrace.h are included before sys/ptrace.h. * sysdeps/unix/sysv/linux/powerpc/sys/ptrace.h: Undefine Linux macros used in __ptrace_request. Signed-off-by: Tulio Magno Quites Machado Filho <tuliom@linux.vnet.ibm.com> (cherry picked from commit 398c6fddafcee2dc4c2b2574417a2d0cfccaeec1)
2018-02-19Add missing "reorder-end" in LC_COLLATE of et_EE [BZ #22517]Mike FABIAN2-0/+7
[BZ #22517] * localedata/locales/et_EE (LC_COLLATE): add missing "reorder-end" (cherry picked from commit 7ec5f9465e732e668d0dc94ac078ba68056d6d0a)
2018-02-21Fix a typo in a comment.Rical Jasan2-1/+5
* io/fcntl.h: Fix a typo in a comment. (cherry picked from commit 0d217f4082473e5fdca87831df928dd525a02f72)
2018-02-19manual: Update the _ISOC99_SOURCE description.Rical Jasan2-4/+6
The current description refers to ISO C99 not being widely adopted, which it is believed to be now. * manual/creature.texi (_ISOC99_SOURCE): Update the dated description. (cherry picked from commit e8d190b9ed81a1b342f0969bc2b5505403183bce)
2018-02-19manual: Document missing feature test macros.Rical Jasan3-2/+48
Several feature test macros are documented in features.h but absent in the manual, and some documented macros accept undocumented values. This commit updates the manual to mention all the accepted macros, along with any values that hold special meaning. * manual/creature.texi (_POSIX_C_SOURCE): Document special values of 199606L, 200112L, and 200809L. (_XOPEN_SOURCE): Document special values of 600 and 700. (_ISOC11_SOURCE): Document macro. (_ATFILE_SOURCE): Likewise. (_FORTIFY_SOURCE): Likewise. (cherry picked from commit 6a3962c4a408e8cbc305d2433711196107374e89) (cherry picked from commit da81ae645d8ee89052f109c814a68a9489f562e6)
2018-03-08NEWS: add entries for bugs 22919 and 22926Dmitry V. Levin1-0/+2
2018-03-09sparc32: Add nop before __startcontext to stop unwinding [BZ #22919]Aurelien Jarno2-0/+19
On sparc32 tst-makecontext fails, as backtrace called within a context created by makecontext to yield infinite backtrace. Fix that the same way than nios2 by adding a nop just before __startcontext. This is needed as otherwise FDE lookup just repeatedly finds __setcontext's FDE in an infinite loop, due to the convention of using 'address - 1' for FDE lookup. Changelog: [BZ #22919] * sysdeps/unix/sysv/linux/sparc/sparc32/setcontext.S (__startcontext): Add nop before __startcontext, add explaining comments. (cherry picked from commit 9aa5c222b9e0409143410a02b6364a3b25dbf028)
2018-03-05powerpc: Fix TLE build for SPE (BZ #22926)Adhemerval Zanella6-2/+23
Some SPE opcodes clashes with some recent PowerISA opcodes and until recently gas did not complain about it. However binutils recently changed it and now VLE configured gas does not support to assembler some instruction that might class with VLE (HTM for instance). It also does not help that glibc build hardware lock elision support as default (regardless of assembler support). Although runtime will not actually enables TLE on SPE hardware (since kernel will not advertise it), I see little advantage on adding HTM support on SPE built glibc. SPE uses an incompatible ABI which does not allow share the same build with default powerpc and HTM code slows down SPE without any benefict. This patch fixes it by only building HTM when SPE configuration is not used. Checked with a powerpc-linux-gnuspe build. I also did some sniff tests on a e500 hardware without any issue. [BZ #22926] * sysdeps/powerpc/powerpc32/sysdep.h (ABORT_TRANSACTION_IMPL): Define empty for __SPE__. * sysdeps/powerpc/sysdep.h (ABORT_TRANSACTION): Likewise. * sysdeps/unix/sysv/linux/powerpc/elision-lock.c (__lll_lock_elision): Do not build hardware transactional code for __SPE__. * sysdeps/unix/sysv/linux/powerpc/elision-trylock.c (__lll_trylock_elision): Likewise. * sysdeps/unix/sysv/linux/powerpc/elision-unlock.c (__lll_unlock_elision): Likewise. Cherry-pick from e921c89e01389161c036ec09112da6e18aeaa688.
2018-02-16manual: Improve documentation of get_current_dir_name. [BZ #6889]Rical Jasan3-8/+15
This is a minor rewording to clarify the behaviour of get_current_dir_name. Additionally, the @vindex is moved above the @deftypefun so that following links give a better result with regard to context. [BZ #6889] * manual/filesys.texi (get_current_dir_name): Clarify behaviour. (cherry picked from commit 7d15ef84f50a80cb170f8ce3457010f59e221cb8)
2018-02-16manual: Fix a syntax error.Rical Jasan2-1/+6
The opening parenthesis for function arguments in an @deftypefun need to be separated from the function name. This isn't just a matter of the GNU coding style---it causes the "(void" (in this case) to be rendered as a part of the function name, causing a visual defect, and also results in a warning to the following effect during `make pdf': Warning: unbalanced parentheses in @def...) * manual/platform.texi (__riscv_flush_icache): Fix @deftypefun syntax. (cherry picked from commit 16efad5171ac1ac2c8728405f2703045f08c494b)
2018-01-24manual: Fix Texinfo warnings about improper node names.Rical Jasan4-6/+12
A number of cross-references to the GCC info manual cause Texinfo warnings; e.g.: ./creature.texi:11: warning: @xref node name should not contain `.' This is due to "gcc.info" being used in the INFO-FILE-NAME (fourth) argument. Changing it to "gcc" removes these warnings. (Manually confirmed equivalent behaviour for make info, html, and pdf.) * manual/creature.texi: Convert references to gcc.info to gcc. * manual/stdio.texi: Likewise. * manual/string.texi: Likewise. (cherry picked from commit 1f6676d7da1b7c864e9a5d59fe9162a88bd21952)
2018-02-18Fix posix/tst-glob_lstat_compat on alpha [BZ #22818]Aurelien Jarno3-0/+14
The tst-glob_lstat_compat test needs to run tests on the previous version of glob. On alpha, there are three versions of glob, GLIBC_2.0, GLIBC_2.1 and GLIBC_2.27, while on other architectures there are only the GLIBC_2.0 and GLIBC_2.27 version. Therefore on alpha the previous version is GLIBC_2.1 and not GLIBC_2.0. Changelog: [BZ #22818] * posix/tst-glob_lstat_compat.c [__alpha__] (glob): Access the GLIBC_2.1 version. (cherry picked from commit f8d79582896c52cc2b50bdd030a3ec27ef23b587)
2018-02-02time: Reference CLOCKS_PER_SEC in clock comment [BZ #22735]Sean McKean3-1/+7
(cherry picked from commit 09e56b9e18f987105e39768f907db800e9330930)
2017-12-29linux/aarch64: sync sys/ptrace.h with Linux 4.15 [BZ #22433]Dmitry V. Levin2-8/+7
Remove compat-specific constants that were never exported by kernel headers under these names. Before linux commit v3.7-rc1~16^2~1 they were exported with COMPAT_ prefix, and since that commit they are not exported at all. * sysdeps/unix/sysv/linux/aarch64/sys/ptrace.h (__ptrace_request): Remove arm-specific PTRACE_GET_THREAD_AREA, PTRACE_GETHBPREGS, and PTRACE_SETHBPREGS. (cherry picked from commit 2fd4bbaa1446f1be700e10c526cf585a796c4991)
2018-02-06NEWS: add an entry for bug 22827Dmitry V. Levin1-0/+1
2018-02-14Update SH libm-tests-ulpsAdhemerval Zanella2-48/+449
* sysdeps/sh/libm-test-ulps: Update. Signed-off-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
2018-02-09[RISC-V] Fix parsing flags in ELF64 files.DJ Delorie2-1/+8
When ldconfig reads Elf64 files to determine the ABI, it used the Elf32 type, so read the wrong location, and stored the wrong ABI type in the cache, making the cache useless. This patch uses an Elf64 type for Elf64 objects instead. Note that pre-patch caches might need to be manually removed and regenerated to get the correct ABIs stored. [BZ #22827] * sysdeps/unix/sysv/linux/riscv/readelflib.c (process_elf_file): Use 64-bit ELF type for 64-bit ELF objects. (cherry picked from commit 6a1ff640dcec04905d8518983ad6252d38b7a733)
2018-05-11Second try at dealing with ancient mktempStan Shebs1-5/+5
2018-05-09Defeat a malloc optimization by declaring things volatile.Stan Shebs5-6/+6
2018-05-09Forestall optimization-out of a buffer.Stan Shebs1-0/+7
2018-05-09Add a clang/lld workaround for symbol not being overriddenStan Shebs1-0/+2
2018-04-20Work around clang mishandling of assert functions in resolver buffer ↵Stan Shebs1-0/+8
allocation, fixes random error returns in resolv/ tests.
2015-10-29Allow suppressing the definition of __USE_FILE_OFFSET64 by defining ↵Manuel Klimek1-1/+3
SUPPRESS_USE_FILE_OFFSET64 in the CROSSTOOL.
2014-03-03For b/5836136, do dlsym(0, "_Unwind..."), i.e. ignore libgcc_s.so.1 dlopen ↵Paul Pluzhnikov1-0/+9
failure.
generated by cgit v1.1 at 2025-02-11 02:26:58 +0000