Dunfell toolchain update analysis
Thanks for the info I requested Sundeep.
Steve or anyone using dunfell,
Do you have any concerns with the updates shown below?
../Randy
---
Hello Randy,
I checked the /Dunfell /branch for gcc, glibc & binutils updates.
1. gcc-9.3 is currently used in Dunfell and gcc-9.5 was released by gcc.
2. glibc-2.31 is used by Dunfell and latest commits in this branch are listed in attached file 'glibc.log'
3. binutils-2.34 is used by Dunfell and latest commits in this branch are listed in attached file 'binutils-gdb.log'
Can I update all these 3 modules as mentioned above?
Thanks,
Sundeep K.
git log --oneline 3ef8be9b89ef98300951741f381eb79126ac029f..d4b75594574ab8a9c2c41209cd8c62aac76b5a04 > glibc.log
d4b7559457 x86-64: Require BMI2 for avx2 functions [BZ #29611]b8bb48a18d x86-64: Require BMI2 for strchr-avx2.S [BZ #29611]c8f2a3e803 Add test for bug 29530e6ae5b25cd Fix memmove call in vfprintf-internal.c:group_number1dbe841a67 Remove most vfprintf width/precision-dependent allocations (bug 14231, bug 26211). 5a802723db stdio: Add tests for printf multibyte convertion leak [BZ#25691] ae7748e67f stdio: Remove memory leak from multibyte convertion [BZ#25691] 174d0b61c7 Linux: Require properly configured /dev/pts for PTYs0a167374fd Linux: Detect user namespace support in io/tst-getcwd-smallbuff 4ad1659d8c getcwd: Set errno to ERANGE for size == 1 (CVE-2021-3999) 3319cea99e support: Add helpers to create paths longer than PATH_MAX f733e291bb support: Fix xclone build failures on ia64 and hppa43757c70ee support: Add xclone29d3aeb0e8 Add xchdir to libsupport.2d7720f316 support: Add create_temp_file_in_dir183709983d NEWS: Add a bug fix entry for BZ #28896d385079bd5 x86: Fix TEST_NAME to make it a string in tst-strncmp-rtm.c 7df3ad6560 x86: Test wcscmp RTM in the wcsncmp overflow case [BZ #28896] fc133fcf49 x86: Fallback {str|wcs}cmp RTM in the ncmp overflow case [BZ #28896] 775c05b28c string: Add a testcase for wcsncmp with SIZE_MAX [BZ #28755] c6b346ec55 x86-64: Test strlen and wcslen with 0 in the RSI register [BZ #28064] 0675185923 x86: Remove wcsnlen-sse4_1 from wcslen ifunc-impl-list [BZ #28064] 5db3239baf x86: Black list more Intel CPUs for TSX [BZ #27398]5b99f172b8 x86: Check RTM_ALWAYS_ABORT for RTM [BZ #28033]70d293a158 NEWS: Add a bug fix entry for BZ #27974a2be2c0f5d String: Add overflow tests for strnlen, memchr, and strncat [BZ #27974] 489006c3c5 x86: Optimize strlen-evex.S937f2c783a x86: Fix overflow bug in wcsnlen-sse4_1 and wcsnlen-avx2 [BZ #27974] 0058c73d11 x86-64: Add wcslen optimize for sse4.1665d0252f1 x86-64: Move strlen.S to multiarch/strlen-vec.S82ff13e2cc x86-64: Fix an unknown vector operation in memchr-evex.S539b593a1d x86: Optimize memchr-evex.S7b37ae60c6 x86: Optimize strlen-avx2.S0381c1c10d x86: Fix overflow bug with wmemchr-sse2 and wmemchr-avx2 [BZ #27974] 10368cb76b x86: Optimize memchr-avx2.S66ca40582e test-strnlen.c: Check that strnlen won't go beyond the maximum length 927bcaf892 test-strnlen.c: Initialize wchar_t string with wmemset [BZ #27655] 0d4159c36c x86-64: Require BMI2 for __strlen_evex and __strnlen_evex c0cbb9345e NEWS: Add a bug fix entry for BZ #27457e81b975fcc x86-64: Fix ifdef indentation in strlen-evex.Saa4e48e73c x86-64: Use ZMM16-ZMM31 in AVX512 memmove family functions ac911d3b57 x86-64: Use ZMM16-ZMM31 in AVX512 memset family functions 20d37de533 x86: Add string/memory function tests in RTM regionfbaa99ed41 x86-64: Add AVX optimized string/memory functions for RTM 096e14f632 x86-64: Add memcmp family functions with 256-bit EVEXf00fad4e4c x86-64: Add memset family functions with 256-bit EVEXcf239ddd2e x86-64: Add memmove family functions with 256-bit EVEX7257ba7bf2 x86-64: Add strcpy family functions with 256-bit EVEXdb9071c0f6 x86-64: Add ifunc-avx2.h functions with 256-bit EVEX2d612b2c5f x86: Set Prefer_No_VZEROUPPER and add Prefer_AVX2_STRCMP5b13651085 NEWS: Add a bug fix entry for BZ #287555ee8a436ab x86: Fix __wcsncmp_avx2 in strcmp-avx2.S [BZ# 28755]
git log --oneline d4b50999b3b287b5f984ade2f8734aa8c9359440..c4e78c0868a22971680217a41fdb73516a26813d > binutils-gdb.log
c4e78c0868a PR27755, powerpc-ld infinite loop33973d228c9 gas, arm: PR26858 Fix availability of single precision vmul/vmla in arm mode 0c8652fe288 x86: Update GNU property tests5c1bd3f52c6 x86: Properly merge -z ibt and -z shstk93b9bf1651a PowerPC TPREL_HA/LO optimisation58950a3bfd4 Date updatee3b314d3a61 aarch64: set sh_entsize of .plt to 026b6ab7a0e4 S/390: z13: Accept vector alignment hints7324292cd94 gas: Fix checking for backwards .org with negative offset463ec189fe9 Prevent a potential use-after-fee memory corruption bug in the linker (for PE format files). ef2826c0fdb Fix the ARM assembler to generate a Realtime profile for armv8-r. 8524bb5bd28 Re: Fix tight loop on recursively-defined symbols5768460022b Fix tight loop on recursively-defined symbolsa72427b1ae0 gas: PR 25863: Fix scalar vmul inside it block when assembling for MVE 9f57ab49b32 BFD: Exclude sections with no content from compress check.aaf3f0599a2 Arm: Fix LSB of GOT for Thumb2 only PLT.97f92b3e90a Arm: Fix thumb2 PLT branch offsets.3053d7a163c include: Sync plugin-api.h with GCCf7aec2b8e09 PR25745, powerpc64-ld overflows string buffer in --stats mode1b2bf0f65c1 include: Sync plugin-api.h with GCC5e8619b9597 include: Sync lto-symtab.h and plugin-api.h with GCC23820109ced plugin: Don't invoke LTO-wrapper64f5c0afcc4 plugin: Use LDPT_ADD_SYMBOLS_V2 to get symbol typeaaa1e160040 Silence warnings due to plugin API changee7c0ee5110c Include: Sync lto-symtab.h and plugin-api.h with GCCb6520be37fd Fix dwarf.c build with GCC 10a560c29ca5a bfd: Change num_group to unsigned int3ca4cd1ebde gas, arm: Fix bad backportb3174859c4b gas, arm: PR25660L Fix vadd/vsub with lt and le condition codes for MVE de9c1b7cfe6 powerpc64-ld infinite loop0318fc4e18e Adjust PR25355 testcase40bfb976274 Re: PR24511, nm should not mark symbols in .init_array as "t"42b2380cdce Don't call lto-wrapper for ar and ranlibacc4a8b8ac8 PR25585, PHDR segment not covered by LOAD segment
Quoted 7 lines · Randy MacLeod
Thanks for the info I requested Sundeep.
Steve or anyone using dunfell,
Do you have any concerns with the updates shown below?
The glibc and binutils updates seem fine. The gcc update(s) concern me a little bit, but we can test and see if any issues arise.
Steve
Quoted 13 lines
Hello Randy,
I checked the Dunfell branch for gcc, glibc & binutils updates.
gcc-9.3 is currently used in Dunfell and gcc-9.5 was released by gcc.
glibc-2.31 is used by Dunfell and latest commits in this branch are listed in attached file 'glibc.log' binutils-2.34 is used by Dunfell and latest commits in this branch are listed in attached file 'binutils-gdb.log'Can I update all these 3 modules as mentioned above?
Thanks,
Sundeep K.
Add Sundeep back after accidentally dropping him from the list.
Quoted 10 lines · Steve Sakoman
Quoted 6 lines · Randy MacLeod
Thanks for the info I requested Sundeep.
Steve or anyone using dunfell,
Do you have any concerns with the updates shown below?
The glibc and binutils updates seem fine. The gcc update(s) concern me a little bit, but we can test and see if any issues arise.
Sure.
The next dunfell build/release dates are:
# YP 3.1.21 build date 2022/11/28
# YP 3.1.21 Release date 2022/12/09
so let's get started.
Sundeep, send the updates with, or followed by, the test results please.
../Randy
Quoted 16 lines
Steve
Quoted 13 lines
Hello Randy,
I checked the Dunfell branch for gcc, glibc & binutils updates.
gcc-9.3 is currently used in Dunfell and gcc-9.5 was released by gcc.
glibc-2.31 is used by Dunfell and latest commits in this branch are listed in attached file 'glibc.log' binutils-2.34 is used by Dunfell and latest commits in this branch are listed in attached file 'binutils-gdb.log'Can I update all these 3 modules as mentioned above?
Thanks,
Sundeep K.
Signature · 2 lines
# Randy MacLeod # Wind River Linux
Quoted 6 lines · Steve Sakoman
Quoted 4 lines · Randy MacLeod
Thanks for the info I requested Sundeep.
Quoted 6 lines
Quoted 3 lines
Steve or anyone using dunfell,
Do you have any concerns with the updates shown below?
The glibc and binutils updates seem fine. The gcc update(s) concern me a little bit, but we can test and see if any issues arise.
The release notes for gcc might concern me if I was trying for super stable .... But, we created some gcc-9.5 recipes and found they fixed a segfault in the fftw QA which offset any concern we had. I'd love to see gcc updated in Dunfel, but if it isn't I plan to create a layer that will overlay the newer gcc in Dunfell to resolve the fftw issue (with 32 arm+neon)
Philip
Quoted 26 lines
Steve
Quoted 23 lines
Hello Randy,
I checked the Dunfell branch for gcc, glibc & binutils updates.
gcc-9.3 is currently used in Dunfell and gcc-9.5 was released by gcc.
glibc-2.31 is used by Dunfell and latest commits in this branch are listed in attached file 'glibc.log' binutils-2.34 is used by Dunfell and latest commits in this branch are listed in attached file 'binutils-gdb.log'Can I update all these 3 modules as mentioned above?
Thanks,
Sundeep K.-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172591): https://lists.openembedded.org/g/openembedded-core/message/172591
Mute This Topic: https://lists.openembedded.org/mt/94732697/384425
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
Quoted 15 lines · Philip Balister
Quoted 6 lines · Steve Sakoman
Quoted 4 lines · Randy MacLeod
Thanks for the info I requested Sundeep.
Quoted 6 lines
Quoted 3 lines
Steve or anyone using dunfell,
Do you have any concerns with the updates shown below?
The glibc and binutils updates seem fine. The gcc update(s) concern me a little bit, but we can test and see if any issues arise.
Quoted 6 lines
The release notes for gcc might concern me if I was trying for super stable .... But, we created some gcc-9.5 recipes and found they fixed a segfault in the fftw QA which offset any concern we had. I'd love to see gcc updated in Dunfel, but if it isn't I plan to create a layer that will overlay the newer gcc in Dunfell to resolve the fftw issue (with 32 arm+neon)
9.5 is a bug fix release in gcc-9 series so it should qualify for stable update for dunfell.
Quoted 32 lines
Philip
Quoted 20 lines
Steve
Quoted 17 lines
Hello Randy,
I checked the Dunfell branch for gcc, glibc & binutils updates.
gcc-9.3 is currently used in Dunfell and gcc-9.5 was released by gcc.
glibc-2.31 is used by Dunfell and latest commits in this branch are listed in attached file 'glibc.log' binutils-2.34 is used by Dunfell and latest commits in this branch are listed in attached file 'binutils-gdb.log'Can I update all these 3 modules as mentioned above?
Thanks,
Sundeep K.-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172817): https://lists.openembedded.org/g/openembedded-core/message/172817
Mute This Topic: https://lists.openembedded.org/mt/94732697/1997914
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-