Get Gentoo!
gentoo.org sites
gentoo.org Wiki Bugs Forums Packages
Planet Archives Sources
Infra Status
summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* [no-patch] Gentoo: Add trigger variable for compiled-locales and warning to ↵gentoo/glibc-2.30-5Andreas K. Hüttel2020-02-161-0/+11
| | | | | | locale-gen Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>
* Gentoo: force -O0 in conform tests to survive $CC changesAndreas K. Hüttel2020-02-162-3/+7
| | | | | | | | | | | | | In bug #659030 Gentoo started passing user's CFLAGS via $CC variable. conform tests should but are not ready to handle -O1/-O2 yet. Tests fail to validate headers due to inlining of weak symbol aliases and other problems. Let's force it back to -O0 until it's fixed upstream. Original patch by Sergei, ported to the new python test framework by Andreas Bug: https://bugs.gentoo.org/659030 Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org> Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>
* Gentoo: Add a C.UTF-8 localeMike FABIAN2020-02-162-0/+239
| | | | | | | | | | | | | | | | | | | | Source: https://src.fedoraproject.org/rpms/glibc/raw/master/f/glibc-c-utf8-locale.patch Notes from there: This patch needs to upstream as part of Carlos O'Donell <carlos@redhat.com>'s work on enabling upstream C.UTF-8 support. This work is currently blocked on cleaning up the test results to prove that full code-point sorting is working as intended. Note that this patch does not provide full code-point sorting as expected. This patch needs to upstream as soon as possible since it would be nice to have this in F29 and fixed. Further information: https://bugzilla.redhat.com/show_bug.cgi?id=902094 https://sourceware.org/bugzilla/show_bug.cgi?id=17318 https://bugs.gentoo.org/671024
* Gentoo: Adapt to Gentoo-specific /etc/mail/aliasesAndreas K. Hüttel2020-02-161-1/+1
| | | | | | | Patch by pacho2 Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org> (cherry picked from commit 4e616cda056f471b799beba2b1cedc787ad4ecc0)
* Gentoo: Disable test that fails because of the gethostbyname4_r revertAndreas K. Hüttel2020-02-161-1/+0
|
* Gentoo: disable tests that fail only in sandboxAndreas K. Hüttel2020-02-166-25/+9
|
* Revert " * sysdeps/posix/getaddrinfo.c (gaih_inet): Only use gethostbyname4_r"Andreas K. Hüttel2020-02-161-7/+2
| | | | | | | | | | | This reverts commit 8479f23aa1d5e5477a37f46823856bdafaedfa46. See for the background https://sourceware.org/bugzilla/show_bug.cgi?id=16826 https://bugs.gentoo.org/show_bug.cgi?id=600632 This makes test resolv/tst-res_use_inet6 fail. Disable it. (cherry picked from commit 06a2a073a2c6fb3e1489af96e125daca248d0a03)
* [no-patch] Gentoo: Add support filesAndreas K. Hüttel2020-02-169-0/+864
| | | | | | | | | * Source: https://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo/src/patchsets/glibc/extra/ * The make-tarball script has been completely rewritten to work with git. * The c-stubs addon has been dropped since the addon mechanism is gone. * Updates to the nscd init script, see Gentoo bug 492814 * Make patchset generation script also work with master * locale-gen: suppress ignored error when emptying already empty directory, bug 647188
* Gentoo: support running tests under sandboxStephanie J. Lockwood-Childs2020-02-163-3/+3
| | | | | | | | | | | | | | | | | when glibc runs its tests, it does so by invoking the local library loader. in Gentoo, we build/run inside of our "sandbox" which itself is linked against libdl (so that it can load libraries and pull out symbols). the trouble is that when you upgrade from an older glibc to the new one, often times internal symbols change name or abi. this is normally OK as you cannot use libc.so from say version 2.3.6 but libpthread.so from say version 2.5, so we always say "keep all of the glibc libraries from the same build". but when glibc runs its tests, it uses dynamic paths to point to its new local copies of libraries. if the test doesnt use libdl, then glibc doesnt add its path, and when sandbox triggers the loading of libdl, glibc does so from the host system system. this gets us into the case of all libraries are from the locally compiled version of glibc except for libdl.so. http://bugs.gentoo.org/56898
* Gentoo: disable ldconfig during installMike Frysinger2020-02-161-0/+1
| | | | | | | | | | Do not bother running ldconfig on DESTDIR. It's a waste of time as we won't use the result (portage will rebuild the cache after install). Also, the Gentoo sandbox does not currently catch chroot() behavior so we end up (incorrectly) flagging it as a violation as a write to /etc. http://sourceware.org/ml/libc-alpha/2012-08/msg00118.html https://bugs.gentoo.org/431038
* riscv: Avoid clobbering register parameters in syscallAdhemerval Zanella2020-02-161-28/+56
| | | | | | | | | | | | | | | | The riscv INTERNAL_SYSCALL macro might clobber the register parameter if the argument itself might clobber any register (a function call for instance). This patch fixes it by using temporary variables for the expressions between the register assignments (as indicated by GCC documentation, 6.47.5.2 Specifying Registers for Local Variables). It is similar to the fix done for MIPS (bug 25523). Checked with riscv64-linux-gnu-rv64imafdc-lp64d build. (cherry picked from commit be74b42ee2a97009a6cd4fc90126add4a41c583b)
* microblaze: Avoid clobbering register parameters in syscallAdhemerval Zanella2020-02-161-35/+56
| | | | | | | | | | | | | | | | The microblaze INTERNAL_SYSCALL macro might clobber the register parameter if the argument itself might clobber any register (a function call for instance). This patch fixes it by using temporary variables for the expressions between the register assignments (as indicated by GCC documentation, 6.47.5.2 Specifying Registers for Local Variables). It is similar to the fix done for MIPS (bug 25523). Checked with microblaze-linux-gnu and microblazeel-linux-gnu build. (cherry picked from commit 6cc8fc7c1506e8084d65b078ff5b05a92e17a28a)
* mips: Fix argument passing for inlined syscalls on Linux [BZ #25523]WANG Xuerui2020-02-164-52/+105
| | | | | | | | | | | | | | | | According to [gcc documentation][1], temporary variables must be used for the desired content to not be call-clobbered. Fix the Linux inline syscall templates by adding temporary variables, much like what x86 did before (commit 381a0c26d73e0f074c962e0ab53b99a6c327066d). Tested with gcc 9.2.0, both cross-compiled and natively on Loongson 3A4000. [1]: https://gcc.gnu.org/onlinedocs/gcc/Local-Register-Variables.html (cherry picked from commit 4fbba6fe904d0094ddc4284066b3860d119cbd4a)
* mips: Use 'long int' and 'long long int' in linux syscall codeWANG Xuerui2020-02-1613-221/+231
| | | | | | Style fixes only, no functional change. (cherry picked from commit d3fbb18aa3164ca1d11e8acba81e1fc2ca70f43e)
* hppa: Align __clone stack argument to 8 bytes (Bug 25066)John David Anglin2020-02-052-2/+8
| | | | | | | | | | | The hppa architecture requires strict alignment for loads and stores. As a result, the minimum stack alignment that will work is 8 bytes. This patch adjusts __clone() to align the stack argument passed to it. It also adjusts slightly some formatting. This fixes the nptl/tst-tls1 test. (cherry picked from commit e4c23a029a54c8c7788eff9ca771a01cccaaa0ce)
* Remove incorrect alloc_size attribute from pvalloc [BZ #25401]Florian Weimer2020-01-174-3/+51
| | | | | | | | | | | | | | | pvalloc is guarantueed to round up the allocation size to the page size, so applications can assume that the memory region is larger than the passed-in argument. The alloc_size attribute cannot express that. The test case is based on a suggestion from Jakub Jelinek. This fixes commit 9bf8e29ca136094f73f69f725f15c51facc97206 ("malloc: make malloc fail with requests larger than PTRDIFF_MAX (BZ#23741)"). Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org> (cherry picked from commit 768c83b7f60d82db6677e19dc51be9f341e0f3fc)
* login: Use pread64 in utmp implementationFlorian Weimer2020-01-171-72/+95
| | | | | | | | | | | | | | | | | This reduces the possible error scenarios considerably because no longer can file seek fail, leaving the file descriptor in an inconsistent state and out of sync with the cache. As a result, it is possible to avoid setting file_offset to -1 to make an error persistent. Instead, subsequent calls will retry the operation and report any errors returned by the kernel. This change also avoids reading the file from the start if pututline is called multiple times, to work around lock acquisition failures due to timeouts. Change-Id: If21ea0c162c38830a89331ea93cddec14c0974de (cherry picked from commit d4625a19fe64f664119a541b317fb83de01bb273)
* Add nocancel version of pread64()Leandro Pereira2020-01-175-2/+41
| | | | | | | | This is in preparation for changes in the dynamic linker so that pread() is used instead of lseek()+read(). Reviewed-by: Carlos O'Donell <carlos@redhat.com> (cherry picked from commit fed33b0fb03d1942a6713286176d42869c0f1580)
* login: Introduce matches_last_entry to utmp processingFlorian Weimer2020-01-171-49/+31
| | | | | | | | | | | | This simplifies internal_getut_nolock and fixes a regression, introduced in commit be6b16d975683e6cca57852cd4cfe715b2a9d8b1 ("login: Acquire write lock early in pututline [BZ #24882]") in pututxline because __utmp_equal can only compare process-related utmp entries. Fixes: be6b16d975683e6cca57852cd4cfe715b2a9d8b1 Change-Id: Ib8a85002f7f87ee41590846d16d7e52bdb82f5a5 (cherry picked from commit 76a7c103eb9060f9e3ba01d073ae4621a17d8b46)
* login: Acquire write lock early in pututline [BZ #24882]Florian Weimer2020-01-174-31/+239
| | | | | | | | | | | | | | It has been reported that due to lack of fairness in POSIX file locking, the current reader-to-writer lock upgrade can result in lack of forward progress. Acquiring the write lock directly hopefully avoids this issue if there are only writers. This also fixes bug 24882 due to the cache revalidation in __libc_pututline. Reviewed-by: Carlos O'Donell <carlos@redhat.com> Change-Id: I57e31ae30719e609a53505a0924dda101d46372e (cherry picked from commit be6b16d975683e6cca57852cd4cfe715b2a9d8b1)
* login: Add nonstring attributes to struct utmp, struct utmpx [BZ #24899]Florian Weimer2020-01-176-10/+33
| | | | | | | | | | Commit 7532837d7b03b3ca5b9a63d77a5bd81dd23f3d9c ("The -Wstringop-truncation option new in GCC 8 detects common misuses") added __attribute_nonstring__ to bits/utmp.h, but it did not update the parallel bits/utmpx.h header. In struct utmp, the nonstring attribute for ut_id was missing. (cherry picked from commit c2adefbafcdd2519ff43eca6891c77cd7b29ab62)
* login: Remove double-assignment of fl.l_whence in try_file_lockFlorian Weimer2020-01-171-1/+1
| | | | | | | | | | Since l_whence is the second member of struct flock, it is written twice. The double-assignment is technically undefined behavior due to the lack of a sequence point. Reviewed-by: Carlos O'Donell <carlos@redhat.com> Change-Id: I2baf9e70690e723c61051b25ccbd510aec15976c (cherry picked from commit b0a83ae71b2588bd2a9e6b40f95191602940e01e)
* login: pututxline could fail to overwrite existing entries [BZ #24902]Florian Weimer2020-01-175-11/+202
| | | | | | | | | | | | | | | | | | | | The internal_getut_r function updates the file_offset variable and therefore must always update last_entry as well. Previously, if pututxline could not upgrade the read lock to a write lock, internal_getut_r would update file_offset only, without updating last_entry, and a subsequent call would not overwrite the existing utmpx entry at file_offset, instead creating a new entry. This has been observed to cause unbounded file growth in high-load situations. This commit removes the buffer argument to internal_getut_r and updates the last_entry variable directly, along with file_offset. Initially reported and fixed by Ondřej Lysoněk. Reviewed-by: Gabriel F. T. Gomes <gabrielftg@linux.ibm.com> (cherry picked from commit 61d3db428176d9d0822e4e680305fe34285edff2)
* login: Use struct flock64 in utmp [BZ #24880]Florian Weimer2020-01-173-2/+9
| | | | | | | | | Commit 06ab719d30b01da401150068054d3b8ea93dd12f ("Fix Linux fcntl OFD locks for non-LFS architectures (BZ#20251)") introduced the use of fcntl64 into the utmp implementation. However, the lock file structure was not updated to struct flock64 at that point. (cherry picked from commit 0d5b2917530ccaf8ad312dfbb7bce69d569c23ad)
* login: Disarm timer after utmp lock acquisition [BZ #24879]Florian Weimer2020-01-173-52/+42
| | | | | | | | | | If the file processing takes a long time for some reason, SIGALRM can arrive while the file is still being processed. At that point, file access will fail with EINTR. Disarming the timer after lock acquisition avoids that. (If there was a previous alarm, it is the responsibility of the caller to deal with the EINTR error.) (cherry picked from commit 628598be7e1bfaa04f34df71ef6678f2c5103dfd)
* login: Fix updwtmp, updwtmx unlockingFlorian Weimer2020-01-174-2/+121
| | | | | | | | | Commit 5a3afa9738f3dbbaf8c0a35665318c1af782111b (login: Replace macro-based control flow with function calls in utmp) introduced a regression because after it, __libc_updwtmp attempts to unlock the wrong file descriptor. (cherry picked from commit 341da5b4b6253de9a7581a066f33f89cacb44dec)
* login: Replace macro-based control flow with function calls in utmpFlorian Weimer2020-01-172-73/+112
| | | | (cherry picked from commit 5a3afa9738f3dbbaf8c0a35665318c1af782111b)
* login: Assume that _HAVE_UT_* constants are trueFlorian Weimer2020-01-1713-302/+138
| | | | | | | | Make the GNU version of bits/utmp.h the generic version because all remaining ports use it (with a sysdeps override for Linux s390/s390x). (cherry picked from commit a33b817f13170b5c24263b92e7e09880fe797d7e)
* login: Remove utmp backend jump tables [BZ #23518]Florian Weimer2020-01-1711-197/+106
| | | | | | | | | There is just one file-based implementation, so this dispatch mechanism is unnecessary. Instead of the vtable pointer __libc_utmp_jump_table, use a non-negative file_fd as the indicator that the backend is initialized. (cherry picked from commit 1a7fe2ebe52b3c8bf465d1756e69452d05c1c103)
* misc/test-errno-linux: Handle EINVAL from quotactlFlorian Weimer2019-12-051-2/+3
| | | | | | | | | | In commit 3dd4d40b420846dd35869ccc8f8627feef2cff32 ("xfs: Sanity check flags of Q_XQUOTARM call"), Linux 5.4 added checking for the flags argument, causing the test to fail due to too restrictive test expectations. Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org> (cherry picked from commit 1f7525d924b608a3e43b10fcfb3d46b8a6e9e4f9)
* <string.h>: Define __CORRECT_ISO_CPP_STRING_H_PROTO for Clang [BZ #25232]Kamlesh Kumar2019-12-052-1/+3
| | | | | | | | | | | | | Without the asm redirects, strchr et al. are not const-correct. libc++ has a wrapper header that works with and without __CORRECT_ISO_CPP_STRING_H_PROTO (using a Clang extension). But when Clang is used with libstdc++ or just C headers, the overloaded functions with the correct types are not declared. This change does not impact current GCC (with libstdc++ or libc++). (cherry picked from commit 953ceff17a4a15b10cfdd5edc3c8cae4884c8ec3)
* x86: Assume --enable-cet if GCC defaults to CET [BZ #25225]Florian Weimer2019-12-033-2/+31
| | | | | | | This links in CET support if GCC defaults to CET. Otherwise, __CET__ is defined, yet CET functionality is not compiled and linked into the dynamic loader, resulting in a linker failure due to undefined references to _dl_cet_check and _dl_open_check.
* libio: Disable vtable validation for pre-2.1 interposed handles [BZ #25203]Florian Weimer2019-11-282-0/+6
| | | | | | | | | | | | | Commit c402355dfa7807b8e0adb27c009135a7e2b9f1b0 ("libio: Disable vtable validation in case of interposition [BZ #23313]") only covered the interposable glibc 2.1 handles, in libio/stdfiles.c. The parallel code in libio/oldstdfiles.c needs similar detection logic. Fixes (again) commit db3476aff19b75c4fdefbe65fcd5f0a90588ba51 ("libio: Implement vtable verification [BZ #20191]"). Change-Id: Ief6f9f17e91d1f7263421c56a7dc018f4f595c21 (cherry picked from commit cb61630ed712d033f54295f776967532d3f4b46a)
* S390: Fix handling of needles crossing a page in strstr z15 ifunc-variant. ↵Stefan Liebler2019-11-272-7/+36
| | | | | | | | | | | | | | | | | | | [BZ #25226] If the specified needle crosses a page-boundary, the s390-z15 ifunc variant of strstr truncates the needle which results in invalid results. This is fixed by loading the needle beyond the page boundary to v18 instead of v16. The bug is sometimes observable in test-strstr.c in check1 and check2 as the haystack and needle is stored on stack. Thus the needle can be on a page boundary. check2 is now extended to test haystack / needles located on stack, at end of page and on two pages. This bug was introduced with commit 6f47401bd5fc71209219779a0426170a9a7395b0 ("S390: Add arch13 strstr ifunc variant.") and is already released in glibc 2.30. (cherry picked from commit bfdb731438206b0f70fe7afa890681155c30b419)
* rtld: Check __libc_enable_secure before honoring LD_PREFER_MAP_32BIT_EXEC ↵Marcin Kościelnicki2019-11-222-1/+11
| | | | | | | | | | (CVE-2019-19126) [BZ #25204] The problem was introduced in glibc 2.23, in commit b9eb92ab05204df772eb4929eccd018637c9f3e9 ("Add Prefer_MAP_32BIT_EXEC to map executable pages with MAP_32BIT"). (cherry picked from commit d5dfad4326fc683c813df1e37bbf5cf920591c8e)
* Don't use a custom wrapper macro around __has_include (bug 25189).Emilio Cobos Álvarez2019-11-223-13/+8
| | | | | | | | | | | | | | | | | | | | | | | | | This causes issues when using clang with -frewrite-includes to e.g., submit the translation unit to a distributed compiler. In my case, I was building Firefox using sccache. See [1] for a reduced test-case since I initially thought this was a clang bug, and [2] for more context. Apparently doing this is invalid C++ per [cpp.cond], which mentions [3]: > The #ifdef and #ifndef directives, and the defined conditional > inclusion operator, shall treat __has_include and __has_cpp_attribute > as if they were the names of defined macros. The identifiers > __has_include and __has_cpp_attribute shall not appear in any context > not mentioned in this subclause. [1]: https://bugs.llvm.org/show_bug.cgi?id=43982 [2]: https://bugs.llvm.org/show_bug.cgi?id=37990 [3]: http://eel.is/c++draft/cpp.cond#7.sentence-2 Change-Id: Id4b8ee19176a9e4624b533087ba870c418f27e60 (cherry picked from commit bfa864e1645e140da2e1aae3cf0d0ba0674f6eb5)
* Base max_fast on alignment, not width, of bins (Bug 24903)DJ Delorie2019-11-191-1/+1
| | | | | | | | | | | | | | set_max_fast sets the "impossibly small" value based on, eventually, MALLOC_ALIGNMENT. The comparisons for the smallest chunk used is, eventually, MIN_CHUNK_SIZE. Note that i386 is the only platform where these are the same, so a smallest chunk *would* be put in a no-fastbins fastbin. This change calculates the "impossibly small" value based on MIN_CHUNK_SIZE instead, so that we can know it will always be impossibly small. (cherry picked from commit ff12e0fb91b9072800f031cb21fb2651ee7b6251)
* malloc: Various cleanups for malloc/tst-mxfastFlorian Weimer2019-11-193-9/+16
| | | | (cherry picked from commit f9769a239784772453d595bc2f4bed8739810e06)
* Add glibc.malloc.mxfast tunableDJ Delorie2019-11-197-7/+96
| | | | | | | | | | | | | * elf/dl-tunables.list: Add glibc.malloc.mxfast. * manual/tunables.texi: Document it. * malloc/malloc.c (do_set_mxfast): New. (__libc_mallopt): Call it. * malloc/arena.c: Add mxfast tunable. * malloc/tst-mxfast.c: New. * malloc/Makefile: Add it. Reviewed-by: Carlos O'Donell <carlos@redhat.com> (cherry picked from commit c48d92b430c480de06762f80c104922239416826)
* malloc: Fix missing accounting of top chunk in malloc_info [BZ #24026]Niklas Hambüchen2019-11-192-0/+12
| | | | | | | | | | | | | | Fixes `<total type="rest" size="..."> incorrectly showing as 0 most of the time. The rest value being wrong is significant because to compute the actual amount of memory handed out via malloc, the user must subtract it from <system type="current" size="...">. That result being wrong makes investigating memory fragmentation issues like <https://bugzilla.redhat.com/show_bug.cgi?id=843478> close to impossible. (cherry picked from commit b6d2c4475d5abc05dd009575b90556bdd3c78ad0)
* mips: Force RWX stack for hard-float builds that can run on pre-4.8 kernelsDragan Mladjenovic2019-11-054-5/+105
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Linux/Mips kernels prior to 4.8 could potentially crash the user process when doing FPU emulation while running on non-executable user stack. Currently, gcc doesn't emit .note.GNU-stack for mips, but that will change in the future. To ensure that glibc can be used with such future gcc, without silently resulting in binaries that might crash in runtime, this patch forces RWX stack for all built objects if configured to run against minimum kernel version less than 4.8. * sysdeps/unix/sysv/linux/mips/Makefile (test-xfail-check-execstack): Move under mips-has-gnustack != yes. (CFLAGS-.o*, ASFLAGS-.o*): New rules. Apply -Wa,-execstack if mips-force-execstack == yes. * sysdeps/unix/sysv/linux/mips/configure: Regenerated. * sysdeps/unix/sysv/linux/mips/configure.ac (mips-force-execstack): New var. Set to yes for hard-float builds with minimum_kernel < 4.8.0 or minimum_kernel not set at all. (mips-has-gnustack): New var. Use value of libc_cv_as_noexecstack if mips-force-execstack != yes, otherwise set to no. (cherry picked from commit 33bc9efd91de1b14354291fc8ebd5bce96379f12)
* Make tst-strftime2 and tst-strftime3 depend on locale generationGabriel F. T. Gomes2019-10-312-0/+8
| | | | | | | | | | | | | Building the test cases in parallel might make tst-strftime2 and tst-strftime3 fail. Simply re-running the test case (or building serially) makes the problem go away. This patch adds the necessary dependency to allow parallel builds in the time subdirectory. Tested for powerpc64le. Reviewed-by: Florian Weimer <fweimer@redhat.com> Reviewed-by: Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com> (cherry picked from commit 52151051b39293dac9fc3181cfd6240d7ce86ca1)
* S390: Add new s390 platform z15.Stefan Liebler2019-10-182-3/+3
| | | | | | | The new IBM z15 is added to platform string array. The macro _DL_PLATFORMS_COUNT is incremented. (cherry picked from commit 2901743568452403849be7295c8732faa7732339)
* Fix RISC-V vfork build with Linux 5.3 kernel headers.Joseph Myers2019-09-202-1/+11
| | | | | | | | | | | | | | | | | | | | | | | Building glibc for RISC-V with Linux 5.3 kernel headers fails because <linux/sched.h>, included in vfork.S for CLONE_* constants, contains a structure definition not safe for inclusion in assembly code. All other architectures already avoid use of that header in vfork.S, either defining the CLONE_* constants locally or embedding the required values directly in the relevant instruction, where they implement vfork using the clone syscall (see the implementations for aarch64, ia64, mips and nios2). This patch makes the RISC-V version define the constants locally like the other architectures. Tested build for all three RISC-V configurations in build-many-glibcs.py with Linux 5.3 headers. * sysdeps/unix/sysv/linux/riscv/vfork.S: Do not include <linux/sched.h>. (CLONE_VM): New macro. (CLONE_VFORK): Likewise. (cherry picked from commit 8cacbcf4a984ccac24efedb795d9c8a7f149d17b)
* alpha: force old OSF1 syscalls for getegid, geteuid and getppid [BZ #24986]Aurelien Jarno2019-09-145-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | On alpha, Linux kernel 5.1 added the standard getegid, geteuid and getppid syscalls (commit ecf7e0a4ad15287). Up to now alpha was using the corresponding OSF1 syscalls through: - sysdeps/unix/alpha/getegid.S - sysdeps/unix/alpha/geteuid.S - sysdeps/unix/alpha/getppid.S When building against kernel headers >= 5.1, the glibc now use the new syscalls through sysdeps/unix/sysv/linux/syscalls.list. When it is then used with an older kernel, the corresponding 3 functions fail. A quick fix is to move the OSF1 wrappers under the sysdeps/unix/sysv/linux/alpha directory so they override the standard linux ones. A better fix would be to try the new syscalls and fallback to the old OSF1 in case the new ones fail. This can be implemented in a later commit. Changelog: [BZ #24986] * sysdeps/unix/alpha/getegid.S: Move to ... * sysdeps/unix/sysv/linux/alpha/getegid.S: ... here. * sysdeps/unix/alpha/geteuid.S: Move to ... * sysdeps/unix/sysv/linux/alpha/geteuid.S: ... here. * sysdeps/unix/alpha/getppid.S: Move to ... * sysdeps/unix/sysv/linux/alpha/getppid.S: ... here (cherry picked from commit 1a6566094d3097f4a3037ab5555cddc6cb11c3a3)
* hppa: Update libm-tests-ulpsAdhemerval Zanella2019-09-082-44/+48
| | | | | | | | The make regen-ulps was done on a PA8900 with 8.3.0. * sysdeps/hppa/fpu/libm-test-ulps: Update. (cherry picked from commit 3175dcc1e67425ad471caddc3d3cfae357de26ff)
* Update Alpha libm-test-ulpsAurelien Jarno2019-09-032-8/+12
| | | | | | | | Changelog: * sysdeps/alpha/fpu/libm-test-ulps: Regenerated using GCC 9.2. (cherry picked from commit b5367a08ae810e3c648fb036f2e5766204f9d83f)
* Chinese locales: Set first_weekday to 2 (bug 24682).Rafal Luzynski2019-08-285-0/+13
| | | | | | | | | | | | | | | | The first day of the week in China (Mainland) should be Monday according to the national standard GB/T 7408-2005. References: * https://www.doc88.com/p-1166696540287.html * https://unicode-org.atlassian.net/browse/CLDR-11510 [BZ #24682] * NEWS: Mention this bug fixed. * localedata/locales/bo_CN (first_weekday): Add, set to 2 (Monday). * localedata/locales/ug_CN (first_weekday): Likewise. * localedata/locales/zh_CN (first_weekday): Likewise. (cherry picked from commit c0fd3244e71db39cef1e2d1d8ba12bb8b7375ce4)
* malloc: Remove unwanted leading whitespace in malloc_info [BZ #24867]Florian Weimer2019-08-013-1/+14
| | | | | | | | It was introduced in commit 6c8dbf00f536d78b1937b5af6f57be47fd376344 ("Reformat malloc to gnu style."). Reviewed-by: Carlos O'Donell <carlos@redhat.com> (cherry picked from commit b0f6679bcd738ea244a14acd879d974901e56c8e)
* Tag 2.30 release.glibc-2.30Carlos O'Donell2019-08-013-3/+7
|