commit c07bf9ef850affda3eea2aab76f89917fb0c80de (HEAD -> gentoo/2.32)
Author: Andreas Schwab <schwab@suse.de>
Date:   Thu Oct 1 13:59:13 2020 +0200

    __vfscanf_internal: fix aliasing violation (bug 26690)
    
    As noted in <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97264>, the cast
    in the call to the read_int function is an aliasing violation.  Change the
    type of local variable f to a pointer to unsigned, which allows to
    eliminate most casts while only adding three new ones.
    
    (cherry picked from commit c0e9ddf59e73e21afe15fca4e94cf7b4b7359bf2)
    
    Reported-by: andy
    Bug: https://bugs.gentoo.org/750992
    Bug: https://sourceware.org/PR26690

 stdio-common/vfscanf-internal.c | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)

commit 419db3d5ec019e8a06d6f1023761e36a627a7a86
Author: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Date:   Mon Nov 2 16:18:29 2020 -0300

    linux: Allow adjtime with NULL argument [BZ #26833]
    
    The adjtime interface allows return the amount of time remaining
    from any previous adjustment that has not yet been completed by
    passing a NULL as first argument.  This was introduced with y2038
    support 0308077e3a.
    
    Checked on i686-linux-gnu.
    
    Reviewed-by: Lukasz Majewski <lukma@denx.de>
    (cherry picked from commit 75a193b7611bade31a150dfcc528b973e3d46231)
    
    Reported-by: Tobias Leupold
    Bug: https://bugs.gentoo.org/756316
    Bug: https://sourceware.org/PR26833

 sysdeps/unix/sysv/linux/adjtime.c | 11 +++++++---
 time/Makefile                     |  3 ++-
 time/tst-adjtime.c                | 44 +++++++++++++++++++++++++++++++++++++++
 3 files changed, 54 insertions(+), 4 deletions(-)

commit a8c329f14c756c6974a5139d3bbdaadb6c9f56a5
Author: Arjun Shankar <arjun@redhat.com>
Date:   Wed Nov 4 12:19:38 2020 +0100

    iconv: Accept redundant shift sequences in IBM1364 [BZ #26224]
    
    The IBM1364, IBM1371, IBM1388, IBM1390 and IBM1399 character sets
    share converter logic (iconvdata/ibm1364.c) which would reject
    redundant shift sequences when processing input in these character
    sets.  This led to a hang in the iconv program (CVE-2020-27618).
    
    This commit adjusts the converter to ignore redundant shift sequences
    and adds test cases for iconv_prog hangs that would be triggered upon
    their rejection.  This brings the implementation in line with other
    converters that also ignore redundant shift sequences (e.g. IBM930
    etc., fixed in commit 692de4b3960d).
    
    Reviewed-by: Carlos O'Donell <carlos@redhat.com>
    (cherry picked from commit 9a99c682144bdbd40792ebf822fe9264e0376fb5)

 NEWS                    |  6 ++++++
 iconv/tst-iconv_prog.sh | 16 ++++++++++------
 iconvdata/ibm1364.c     | 14 ++------------
 3 files changed, 18 insertions(+), 18 deletions(-)

commit 674a051466e7ff1d4424c24d103f456a512f3f44
Author: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Date:   Wed Nov 25 15:00:44 2020 -0300

    sh: Add sh4 fpu Implies folder
    
    The commit 605f38177db (sh: Split BE/LE abilist) did not take in
    consideration the SH4 fpu support.
    
    Checked with a build for sh4-linux-gnu and manually checked that
    the implementations at sysdeps/sh/sh4/fpu/ are selected.
    
    John Paul Adrian Glaubitz also confirmed it fixes the build issues
    he encontered.
    
    (cherry-picked from 9ff2674ef82eccd5ae5dfa6bb733c0e3613764c6)

 NEWS                                          | 1 +
 sysdeps/sh/be/sh4/fpu/Implies                 | 1 +
 sysdeps/sh/le/sh4/fpu/Implies                 | 1 +
 sysdeps/unix/sysv/linux/sh/be/sh4/fpu/Implies | 1 +
 sysdeps/unix/sysv/linux/sh/le/sh4/fpu/Implies | 1 +
 5 files changed, 5 insertions(+)

commit 144a4e0522111e8c03cfeb408d4af3db65b568e7
Author: Florian Weimer <fweimer@redhat.com>
Date:   Wed Nov 11 11:59:11 2020 +0100

    struct _Unwind_Exception alignment should not depend on compiler flags
    
    __attribute__((__aligned__)) selects an alignment that depends on
    the micro-architecture selected by GCC flags.  Enabling vector
    extensions may increase the allignment.  This is a problem when
    building glibc as a collection of ELF multilibs with different
    GCC flags because ld.so and libc.so/libpthread.so/&c may end up
    with a different layout of struct pthread because of the
    changing offset of its struct _Unwind_Exception field.
    
    Tested-By: Matheus Castanho <msc@linux.ibm.com>
    
    (cherry picked from commit 30af7c7fa13e17d82c3f1f91536384715844f432)

 sysdeps/generic/unwind.h | 24 +++++++++++++++---------
 1 file changed, 15 insertions(+), 9 deletions(-)

commit f785972d9bd71469d7c349d42e65187959aa91d4
Author: Florian Weimer <fweimer@redhat.com>
Date:   Thu Oct 15 12:33:13 2020 +0200

    resolv: Serialize processing in resolv/tst-resolv-txnid-collision
    
    When switching name servers, response processing by two server
    threads clobbers the global test state.  (There is still some
    risk that this test is negatively impact by packet drops and
    packet reordering, but this applies to many of the resolver tests
    and is difficult to avoid.)
    
    Fixes commit f1f00c072138af90ae6da180f260111f09afe7a3 ("resolv:
    Handle transaction ID collisions in parallel queries (bug 26600)").
    
    (cherry picked from commit b8b53b338f6da91e86d115a39da860cefac736ad)

 resolv/tst-resolv-txnid-collision.c | 5 +++++
 1 file changed, 5 insertions(+)

commit 624b26f377520bbbb2449540f875b1055079be2a
Author: Florian Weimer <fweimer@redhat.com>
Date:   Wed Oct 14 10:54:39 2020 +0200

    resolv: Handle transaction ID collisions in parallel queries (bug 26600)
    
    If the transaction IDs are equal, the old check attributed both
    responses to the first query, not recognizing the second response.
    This fixes bug 26600.
    
    (cherry picked from commit f1f00c072138af90ae6da180f260111f09afe7a3)

 NEWS                                |   1 +
 resolv/Makefile                     |   7 +
 resolv/res_send.c                   |  40 ++---
 resolv/tst-resolv-txnid-collision.c | 329 ++++++++++++++++++++++++++++++++++++
 4 files changed, 357 insertions(+), 20 deletions(-)

commit f5d4fcb1c6c8a40827b6a5c579c7da4376715346
Author: Florian Weimer <fweimer@redhat.com>
Date:   Wed Oct 14 10:54:39 2020 +0200

    support: Provide a way to clear the RA bit in DNS server responses
    
    (cherry picked from commit 08443b19965f48862b02c2fd7b33a39d66daf2ff)

 support/resolv_test.c | 4 +++-
 support/resolv_test.h | 4 ++++
 2 files changed, 7 insertions(+), 1 deletion(-)

commit 76a5da8671f4b27263eaafb2712d9e0d3658a8c6
Author: Florian Weimer <fweimer@redhat.com>
Date:   Wed Oct 14 10:54:39 2020 +0200

    support: Provide a way to reorder responses within the DNS test server
    
    (cherry picked from commit 873e239a4c3d8ec235c27439c1bdc5bbf8aa1818)

 support/Makefile                            |  2 +
 support/resolv_response_context_duplicate.c | 37 ++++++++++++++++++
 support/resolv_response_context_free.c      | 28 ++++++++++++++
 support/resolv_test.c                       | 59 ++++++++++++++++++-----------
 support/resolv_test.h                       | 37 +++++++++++++++---
 5 files changed, 135 insertions(+), 28 deletions(-)

commit 0e867fccfffcfac22446b3e8448d6b178b254735
Author: Siddhesh Poyarekar <siddhesh@sourceware.org>
Date:   Thu Nov 5 10:20:32 2020 +0530

    Remove __warndecl
    
    The macro is not used anymore, so remove it and warning-nop.c.
    
    Reviewed-by: Florian Weimer <fweimer@redhat.com>
    
    (cherry-picked from 34aec973e15a81926198f4b71ff99081dff87a92)

 debug/Makefile      |  2 +-
 debug/warning-nop.c | 70 -----------------------------------------------------
 misc/sys/cdefs.h    |  3 ---
 3 files changed, 1 insertion(+), 74 deletions(-)

commit 3ec3ae21127f859272ca62df39caa4c62dc84a4d
Author: Siddhesh Poyarekar <siddhesh@sourceware.org>
Date:   Tue Nov 3 15:09:28 2020 +0530

    Remove __warn_memset_zero_len [BZ #25399]
    
    Non-gcc compilers (clang and possibly other compilers that do not
    masquerade as gcc 5.0 or later) are unable to use
    __warn_memset_zero_len since the symbol is no longer available on
    glibc built with gcc 5.0 or later.  While it was likely an oversight
    that caused this omission, the fact that it wasn't noticed until
    recently (when clang closed the gap on _FORTIFY_SUPPORT) that the
    symbol was missing.
    
    Given that both gcc and clang are capable of doing this check in the
    compiler, drop all remaining signs of __warn_memset_zero_len from
    glibc so that no more objects are built with this symbol in future.
    
    (cherry-picked from dc274b141666766b8ef70992d887e3c0c5e41bed)

 string/bits/string_fortified.h | 15 ---------------
 1 file changed, 15 deletions(-)

commit 24723906424251ecf1f6bdcc6da5f3fe1da38064
Author: Florian Weimer <fweimer@redhat.com>
Date:   Mon Nov 9 11:31:04 2020 +0100

    aarch64: Add unwind information to _start (bug 26853)
    
    This adds CFI directives which communicate that the stack ends
    with this function.
    
    Fixes bug 26853.
    
    (cherry picked from commit 5edf3d9fd6efe06fda37b2a460e60690a90457a4)

 NEWS                    | 1 +
 sysdeps/aarch64/start.S | 7 +++----
 2 files changed, 4 insertions(+), 4 deletions(-)

commit b37d61225301b7c531c95d1d3610da90c58dfd1d
Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Date:   Thu Oct 22 17:55:01 2020 +0100

    aarch64: Fix DT_AARCH64_VARIANT_PCS handling [BZ #26798]
    
    The variant PCS support was ineffective because in the common case
    linkmap->l_mach.plt == 0 but then the symbol table flags were ignored
    and normal lazy binding was used instead of resolving the relocs early.
    (This was a misunderstanding about how GOT[1] is setup by the linker.)
    
    In practice this mainly affects SVE calls when the vector length is
    more than 128 bits, then the top bits of the argument registers get
    clobbered during lazy binding.
    
    Fixes bug 26798.
    
    (cherry picked from commit 558251bd8785760ad40fcbfeaaee5d27fa5b0fe4)

 sysdeps/aarch64/dl-machine.h | 12 ++++--------
 1 file changed, 4 insertions(+), 8 deletions(-)

commit 3ce194a510a81f6d557619747c8a64b750d88ca2 (gentoo/gentoo/2.32)
Author: Sajan Karumanchi <sajan.karumanchi@amd.com>
Date:   Wed Oct 28 13:05:33 2020 +0530

    x86: Optimizing memcpy for AMD Zen architecture.
    
    Modifying the shareable cache '__x86_shared_cache_size', which is a
    factor in computing the non-temporal threshold parameter
    '__x86_shared_non_temporal_threshold' to optimize memcpy for AMD Zen
    architectures.
    In the existing implementation, the shareable cache is computed as 'L3
    per thread, L2 per core'. Recomputing this shareable cache as 'L3 per
    CCX(Core-Complex)' has brought in performance gains.
    As per the large bench variant results, this patch also addresses the
    regression problem on AMD Zen architectures.
    
    Backport of commit 59803e81f96b479c17f583b31eac44b57591a1bf upstream,
    with the fix from cb3a749a22a55645dc6a52659eea765300623f98 ("x86:
    Restore processing of cache size tunables in init_cacheinfo") applied.
    
    Reviewed-by: Premachandra Mallappa <premachandra.mallappa@amd.com>
    Co-Authored-by: Florian Weimer <fweimer@redhat.com>
    (cherry picked from commit 8813b2682e4094e43b0cf1634e99619f1b8b2c62)

 sysdeps/x86/cacheinfo.c | 20 +++++++++++++++++---
 1 file changed, 17 insertions(+), 3 deletions(-)

commit f8fe2d39c65841aaa3f96faad2860998f6f32a81
Author: Patrick McGehearty <patrick.mcgehearty@oracle.com>
Date:   Mon Sep 28 20:11:28 2020 +0000

    Reversing calculation of __x86_shared_non_temporal_threshold
    
    The __x86_shared_non_temporal_threshold determines when memcpy on x86
    uses non_temporal stores to avoid pushing other data out of the last
    level cache.
    
    This patch proposes to revert the calculation change made by H.J. Lu's
    patch of June 2, 2017.
    
    H.J. Lu's patch selected a threshold suitable for a single thread
    getting maximum performance. It was tuned using the single threaded
    large memcpy micro benchmark on an 8 core processor. The last change
    changes the threshold from using 3/4 of one thread's share of the
    cache to using 3/4 of the entire cache of a multi-threaded system
    before switching to non-temporal stores. Multi-threaded systems with
    more than a few threads are server-class and typically have many
    active threads. If one thread consumes 3/4 of the available cache for
    all threads, it will cause other active threads to have data removed
    from the cache. Two examples show the range of the effect. John
    McCalpin's widely parallel Stream benchmark, which runs in parallel
    and fetches data sequentially, saw a 20% slowdown with this patch on
    an internal system test of 128 threads. This regression was discovered
    when comparing OL8 performance to OL7.  An example that compares
    normal stores to non-temporal stores may be found at
    https://vgatherps.github.io/2018-09-02-nontemporal/.  A simple test
    shows performance loss of 400 to 500% due to a failure to use
    nontemporal stores. These performance losses are most likely to occur
    when the system load is heaviest and good performance is critical.
    
    The tunable x86_non_temporal_threshold can be used to override the
    default for the knowledgable user who really wants maximum cache
    allocation to a single thread in a multi-threaded system.
    The manual entry for the tunable has been expanded to provide
    more information about its purpose.
    
            modified: sysdeps/x86/cacheinfo.c
            modified: manual/tunables.texi
    
    (cherry picked from commit d3c57027470b78dba79c6d931e4e409b1fecfc80)
    (cherry picked from commit e61a8fd8fadbf1a8cef997a0f921575cb2905ea2)

 manual/tunables.texi    |  6 +++++-
 sysdeps/x86/cacheinfo.c | 16 +++++++++++-----
 2 files changed, 16 insertions(+), 6 deletions(-)

commit dba2b6c84cbe5ee9ca330d22ed0fc2b5bbbb490e
Author: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Date:   Tue Sep 29 14:51:36 2020 -0300

    sysvipc: Fix IPC_INFO and SHM_INFO handling [BZ #26636]
    
    Both commands are Linux extensions where the third argument is either
    a 'struct shminfo' (IPC_INFO) or a 'struct shm_info' (SHM_INFO) instead
    of 'struct shmid_ds'.  And their information does not contain any time
    related fields, so there is no need to extra conversion for __IPC_TIME64.
    
    The regression testcase checks for Linux specifix SysV ipc message
    control extension.  For SHM_INFO it tries to match the values against the
    tunable /proc values and for MSG_STAT/MSG_STAT_ANY it check if the create\
    shared memory is within the global list returned by the kernel.
    
    Checked on x86_64-linux-gnu and on i686-linux-gnu (Linux v5.4 and on
    Linux v4.15).
    
    (cherry picked from commit  a49d7fd4f764e97ccaf922e433046590ae52fce9)
    (cherry picked from commit 0b9460d22e285432d232f42c7442a3226e1bf830)

 NEWS                                        |   2 +
 sysdeps/unix/sysv/linux/Makefile            |   2 +-
 sysdeps/unix/sysv/linux/shmctl.c            |  24 +++-
 sysdeps/unix/sysv/linux/tst-sysvshm-linux.c | 185 ++++++++++++++++++++++++++++
 4 files changed, 206 insertions(+), 7 deletions(-)

commit 82f3f5fc3b0b0983ae19731575eb8af8c73e645d
Author: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Date:   Tue Sep 29 14:39:56 2020 -0300

    sysvipc: Fix IPC_INFO and MSG_INFO handling [BZ #26639]
    
    Both commands are Linux extensions where the third argument is a
    'struct msginfo' instead of 'struct msqid_ds' and its information
    does not contain any time related fields (so there is no need to
    extra conversion for __IPC_TIME64.
    
    The regression testcase checks for Linux specifix SysV ipc message
    control extension.  For IPC_INFO/MSG_INFO it tries to match the values
    against the tunable /proc values and for MSG_STAT/MSG_STAT_ANY it
    check if the create message queue is within the global list returned
    by the kernel.
    
    Checked on x86_64-linux-gnu and on i686-linux-gnu (Linux v5.4 and on
    Linux v4.15).
    
    (cherry picked from commit 20a00dbefca5695cccaa44846a482db8ccdd85ab)
    (cherry picked from commit c4aeedea598a1bd80f52ca9ebd07fe447680d491)

 NEWS                                        |   1 +
 sysdeps/unix/sysv/linux/Makefile            |   2 +-
 sysdeps/unix/sysv/linux/msgctl.c            |  22 +++-
 sysdeps/unix/sysv/linux/tst-sysvmsg-linux.c | 177 ++++++++++++++++++++++++++++
 4 files changed, 197 insertions(+), 5 deletions(-)

commit 16fa2ec52e3972558d93d2869c909ca055b9f745
Author: Dmitry V. Levin <ldv@altlinux.org>
Date:   Tue Sep 29 14:10:20 2020 -0300

    sysvipc: Fix SEM_STAT_ANY kernel argument pass [BZ #26637]
    
    Handle SEM_STAT_ANY the same way as SEM_STAT so that the buffer argument
    of SEM_STAT_ANY is properly passed to the kernel and back.
    
    The regression testcase checks for Linux specifix SysV ipc message
    control extension.  For IPC_INFO/SEM_INFO it tries to match the values
    against the tunable /proc values and for SEM_STAT/SEM_STAT_ANY it
    check if the create message queue is within the global list returned
    by the kernel.
    
    Checked on x86_64-linux-gnu and on i686-linux-gnu (Linux v5.4 and on
    Linux v4.15).
    
    Co-authored-by: Adhemerval Zanella  <adhemerval.zanella@linaro.org>
    
    (cherry picked from commit 574500a108be1d2a6a0dc97a075c9e0a98371aba)
    (cherry picked from commit 9b139b6b81a5def91bec01f30301acc95fbf0289)

 NEWS                                        |   2 +
 sysdeps/unix/sysv/linux/Makefile            |   2 +-
 sysdeps/unix/sysv/linux/semctl.c            |   6 +
 sysdeps/unix/sysv/linux/tst-sysvsem-linux.c | 184 ++++++++++++++++++++++++++++
 sysvipc/test-sysvsem.c                      |   1 +
 5 files changed, 194 insertions(+), 1 deletion(-)

commit 8f148125478118b8b41260a8df3cd899cb49c3c7
Author: Wilco Dijkstra <wdijkstr@arm.com>
Date:   Wed Oct 14 13:56:21 2020 +0100

    AArch64: Use __memcpy_simd on Neoverse N2/V1
    
    Add CPU detection of Neoverse N2 and Neoverse V1, and select __memcpy_simd as
    the memcpy/memmove ifunc.
    
    Reviewed-by: Adhemerval Zanella  <adhemerval.zanella@linaro.org>
    (cherry picked from commit e11ed9d2b4558eeacff81557dc9557001af42a6b)
    (cherry picked from commit 81c5484d93a7768a8acc4cfdc228d925d60cd906)

 sysdeps/aarch64/multiarch/memcpy.c             | 3 ++-
 sysdeps/aarch64/multiarch/memmove.c            | 3 ++-
 sysdeps/unix/sysv/linux/aarch64/cpu-features.h | 4 ++++
 3 files changed, 8 insertions(+), 2 deletions(-)

commit 538fe433fbc658ccc4f3cf52e83e0f1633066a7d
Author: Wilco Dijkstra <wdijkstr@arm.com>
Date:   Fri Aug 28 17:51:40 2020 +0100

    AArch64: Improve backwards memmove performance
    
    On some microarchitectures performance of the backwards memmove improves if
    the stores use STR with decreasing addresses.  So change the memmove loop
    in memcpy_advsimd.S to use 2x STR rather than STP.
    
    Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
    (cherry picked from commit bd394d131c10c9ec22c6424197b79410042eed99)
    (cherry picked from commit 0f8f0ed25c196cfb93edf461aefdad15314ae05c)

 sysdeps/aarch64/multiarch/memcpy_advsimd.S | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

commit db28f19b5386bd8837f9a8bf413f447c834b39d2
Author: Carlos O'Donell <carlos@redhat.com>
Date:   Fri Oct 2 09:23:35 2020 -0400

    Set version.h RELEASE to "stable" (Bug 26700)
    
    The RELEASE macro was accidentaly set to "release" instead of
    the expected "stable" by the release manager.  This is a mistake
    that leads to the build using "-g -O1" instead of "-g -O2" if
    configure was executed with "CFLAGS=" (CFLAGS set but empty).
    
    (cherry picked from commit 23482f788665df83edc8b542698f45fed45a2711)

 version.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

commit e8dfb81a462a82b268c4ab0f8ac96fbb81a8e8fa
Author: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Date:   Mon Aug 31 11:53:51 2020 -0300

    string: Fix strerrorname_np return value [BZ #26555]
    
    It returns the string of the error constant, not its description (as
    strerrordesc_np).  To handle the Hurd error mapping, the ERR_MAP was
    removed from errlist.h to errlist.c.
    
    Also, the testcase test-strerr (added on 325081b9eb2) was not added
    on the check build neither it builds correctly.  This patch also
    changed it to decouple from errlist.h, the expected return values
    are added explicitly for both both strerrorname_np and strerrordesc_np
    directly.
    
    Checked on x86_64-linux-gnu and i686-linux-gnu.  I also run a make
    check for i686-gnu.
    
    (cherry picked from commit cef95fdc2e4002ee6357d8d40ef73c8d875720e3)
    (cherry picked from commit 69beb5cbf85cae1c61fe7432500ac10880dc7b07)

 NEWS                       |   1 +
 stdio-common/Makefile      |   3 +-
 stdio-common/errlist.c     |  13 +-
 stdio-common/test-strerr.c | 690 ++++++++++++++++++++++++++++++++++++++++++---
 sysdeps/gnu/errlist.h      | 301 ++++++++++----------
 5 files changed, 819 insertions(+), 189 deletions(-)

commit 3559d1740c9f0a5ebd4dafda37ac88c0cd137d81
Author: Arjun Shankar <arjun@redhat.com>
Date:   Fri Sep 25 14:47:06 2020 +0200

    intl: Handle translation output codesets with suffixes [BZ #26383]
    
    Commit 91927b7c7643 (Rewrite iconv option parsing [BZ #19519]) did not
    handle cases where the output codeset for translations (via the `gettext'
    family of functions) might have a caller specified encoding suffix such as
    TRANSLIT or IGNORE.  This led to a regression where translations did not
    work when the codeset had a suffix.
    
    This commit fixes the above issue by parsing any suffixes passed to
    __dcigettext and adds two new test-cases to intl/tst-codeset.c to
    verify correct behaviour.  The iconv-internal function __gconv_create_spec
    and the static iconv-internal function gconv_destroy_spec are now visible
    internally within glibc and used in intl/dcigettext.c.
    
    (cherry picked from commit 7d4ec75e111291851620c6aa2c4460647b7fd50d)
    (cherry picked from commit fe62c4d173f3cc1ac64f01e75a8f421b2f092cdb)
    Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>

 iconv/Versions        |  4 +++-
 iconv/gconv_charset.c | 10 ++++++++++
 iconv/gconv_charset.h | 27 ---------------------------
 iconv/gconv_int.h     | 21 +++++++++++++++++++++
 iconv/iconv_open.c    |  2 +-
 iconv/iconv_prog.c    |  2 +-
 intl/dcigettext.c     | 17 ++++++++++-------
 intl/tst-codeset.c    | 34 ++++++++++++++--------------------
 8 files changed, 60 insertions(+), 57 deletions(-)

commit 7ff93707e2aec8c24ad9091c0d7f9567c20f0e8e (tag: gentoo/glibc-2.32-2)
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Wed Aug 26 04:26:50 2020 +0200

    NEWS: Update for [BZ #26534] fix
    
    (cherry picked from commit 386543bc4495f658dcce6cd4d11e4ba6574a46f5)

 NEWS | 5 +++++
 1 file changed, 5 insertions(+)

commit 5752df8c01162de92e83a031f61e4441b4ea432b
Author: Ondřej Hošek <ondra.hosek@gmail.com>
Date:   Wed Aug 26 04:26:50 2020 +0200

    x86-64: Fix FMA4 detection in ifunc [BZ #26534]
    
    A typo in commit 107e6a3c2212ba7a3a4ec7cae8d82d73f7c95d0b causes the
    FMA4 code path to be taken on systems that support FMA, even if they do
    not support FMA4. Fix this to detect FMA4.
    
    (cherry picked from commit 23af890b3f04e80da783ba64e6b6d94822e01d54)
    
    Reported-by: Sven E.
    Bug: https://bugs.gentoo.org/740110
    Bug: https://sourceware.org/PR26534
    Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>

 sysdeps/x86_64/fpu/multiarch/ifunc-fma4.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

commit 205e8b79e88d93cae937fe455c112f0bbadb151a (tag: gentoo/glibc-2.32-1)
Author: Sergei Trofimovich <slyfox@gentoo.org>
Date:   Sat Jul 11 20:06:51 2020 +0300

    Fix miscompilation on ia64's gcc-10
    
    Bug: https://bugs.gentoo.org/723268
    Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>

 sysdeps/unix/sysv/linux/ia64/dl-sysdep.h | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

commit cfb9d31098f1afc0af4ae1f1279d5a02a7c02ad2
Author: Andreas K. Hüttel <dilfridge@gentoo.org>
Date:   Fri Dec 14 20:43:04 2018 +0100

    Force -O0 in conform tests to survive $CC changes
    
    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>

 conform/conformtest.py   | 6 ++++--
 conform/linknamespace.py | 4 +++-
 2 files changed, 7 insertions(+), 3 deletions(-)

commit 9648a6846058b4bcf966fbb473d8e913731cf48c
Author: Mike FABIAN <mfabian@redhat.com>
Date:   Mon Aug 10 15:58:12 2015 +0200

    Add C.UTF-8 locale
    
    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

 localedata/SUPPORTED |   1 +
 localedata/locales/C | 238 +++++++++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 239 insertions(+)

commit 53c24c85125de3084a1581e49516b7fbcceb0158
Author: Andreas K. Hüttel <dilfridge@gentoo.org>
Date:   Mon Oct 22 22:34:13 2018 +0200

    Adapt to Gentoo-specific /etc/mail/aliases
    
    Patch by pacho2
    
    Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>
    (cherry picked from commit 4e616cda056f471b799beba2b1cedc787ad4ecc0)

 nss/nss_files/files-alias.c    |  2 +-
 nss/tst-nss-files-alias-leak.c | 18 +++++++++---------
 support/support_chroot.c       |  8 +++++++-
 3 files changed, 17 insertions(+), 11 deletions(-)

commit b51bd4a5bc55428bac6aa7ea9021ef080caa6f1f
Author: Andreas K. Hüttel <dilfridge@gentoo.org>
Date:   Tue Aug 29 22:58:50 2017 +0200

    Revert " * sysdeps/posix/getaddrinfo.c (gaih_inet): Only use gethostbyname4_r"
    
    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 tst-nss-files-hosts-multi fail. Disable it.

 nss/Makefile                | 1 -
 sysdeps/posix/getaddrinfo.c | 9 ++-------
 2 files changed, 2 insertions(+), 8 deletions(-)

commit c47088f8d9bee6aac782dbf3d4c967677fcc7574
Author: Mike Frysinger <vapier@gentoo.org>
Date:   Wed Apr 1 02:15:48 2009 -0400

    Disable ldconfig during install
    
    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

 Makefile | 1 +
 1 file changed, 1 insertion(+)
