[Bug ld/31982] [2.43 Regression] mir 2.17 build failure during an LTO enabled build
https://sourceware.org/bugzilla/show_bug.cgi?id=31982 Matthias Klose changed: What|Removed |Added Status|WAITING |NEW --- Comment #7 from Matthias Klose --- $ readelf --dyn-syms -W /lib/aarch64-linux-gnu/libstdc++.so.6.0.33 | grep _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEC.EPKcmRKS3_ 1741: 0016738060 FUNCWEAK DEFAULT 13 _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEC2EPKcmRKS3_@@GLIBCXX_3.4.21 4088: 0016738060 FUNCWEAK DEFAULT 13 _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEC1EPKcmRKS3_@@GLIBCXX_3.4.21 $ readelf --dyn-syms -W /lib/aarch64-linux-gnu/libstdc++.so.6.0.33 | grep _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEC.EPKcmRKS3_|c++filt 1741: 0016738060 FUNCWEAK DEFAULT 13 std::__cxx11::basic_string, std::allocator >::basic_string(char const*, unsigned long, std::allocator const&)@@GLIBCXX_3.4.21 4088: 0016738060 FUNCWEAK DEFAULT 13 std::__cxx11::basic_string, std::allocator >::basic_string(char const*, unsigned long, std::allocator const&)@@GLIBCXX_3.4.21 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/31982] [2.43 Regression] mir 2.17 build failure during an LTO enabled build
https://sourceware.org/bugzilla/show_bug.cgi?id=31982 Jonathan Wakely changed: What|Removed |Added CC||jwakely.gcc at gmail dot com -- You are receiving this mail because: You are on the CC list for the bug.
[Bug libctf/32093] -Walloc-size warning in ctf-hash.c
https://sourceware.org/bugzilla/show_bug.cgi?id=32093 --- Comment #1 from Sourceware Commits --- The master branch has been updated by Alan Modra : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=35e273526b7d4e345bb77a042af093508dad57f4 commit 35e273526b7d4e345bb77a042af093508dad57f4 Author: Alan Modra Date: Thu Aug 29 11:08:44 2024 +0930 PR32093, -Walloc-size warning in ctf-hash.c PR 32093 * ctf-hash.c (ctf_dynhash_create_sized, ctf_hashtab_insert): Avoid -Walloc-size warning. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/31982] [2.43 Regression] mir 2.17 build failure during an LTO enabled build
https://sourceware.org/bugzilla/show_bug.cgi?id=31982 --- Comment #8 from H.J. Lu --- (In reply to Matthias Klose from comment #5) > fails with > > /usr/bin/ld: /tmp/ccijjp3k.ltrans5.ltrans.o: in function > `StaticDisplayConfig_nonexistent_config_file_is_no_error_Test::TestBody()': > /usr/src/mir-2.14.1-7/tests/miral/static_display_config.cpp:154:(. > text+0x6d94): warning: the use of `tmpnam' is dangerous, better use `mkstemp' > /usr/bin/ld: ../libmir-test-assist.a(mmap_wrapper.cpp.o): in function > `std::literals::string_literals::operator"" s[abi:cxx11](char const*, > unsigned long)': > /usr/include/c++/14/bits/basic_string.h:4694:(.text+0x6f8): undefined > reference to `std::__cxx11::basic_string, > std::allocator >::basic_string(char const*, unsigned long, > std::allocator const&)' > /usr/bin/ld: /usr/include/c++/14/bits/basic_string.h:4694:(.text+0xa64): > undefined reference to `std::__cxx11::basic_string std::char_traits, std::allocator >::basic_string(char const*, > unsigned long, std::allocator const&)' > collect2: error: ld returned 1 exit status I can't reproduce it on Fedora 40/x86-64. It may have something to do with how your GCC is configured and the command-line options passed to linker. Please show the output of # gcc -v as well as pass -v to the final link command and show the full linker command line. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/31982] [2.43 Regression] mir 2.17 build failure during an LTO enabled build
https://sourceware.org/bugzilla/show_bug.cgi?id=31982 --- Comment #9 from Matthias Klose --- Created attachment 15688 --> https://sourceware.org/bugzilla/attachment.cgi?id=15688&action=edit log of the build -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/31982] [2.43 Regression] mir 2.17 build failure during an LTO enabled build
https://sourceware.org/bugzilla/show_bug.cgi?id=31982 --- Comment #10 from Matthias Klose --- $ gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/aarch64-linux-gnu/14/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none OFFLOAD_TARGET_DEFAULT=1 Target: aarch64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 14.2.0-3ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-14/README.Bugs --enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2,rust --prefix=/usr --with-gcc-major-version-only --program-suffix=-14 --program-prefix=aarch64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/libexec --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-libstdcxx-backtrace --enable-gnu-unique-object --disable-libquadmath --disable-libquadmath-support --enable-plugin --enable-default-pie --with-system-zlib --enable-libphobos-checking=release --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --enable-fix-cortex-a53-843419 --disable-werror --enable-offload-targets=nvptx-none=/build/gcc-14-3heZVg/gcc-14-14.2.0/debian/tmp-nvptx/usr --enable-offload-defaulted --without-cuda-driver --enable-checking=release --build=aarch64-linux-gnu --host=aarch64-linux-gnu --target=aarch64-linux-gnu --with-build-config=bootstrap-lto-lean --enable-link-serialization=2 Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 14.2.0 (Ubuntu 14.2.0-3ubuntu1) -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/32123] New: Linker should check all invalid @TLSCALL usage
https://sourceware.org/bugzilla/show_bug.cgi?id=32123 Bug ID: 32123 Summary: Linker should check all invalid @TLSCALL usage Product: binutils Version: 2.44 (HEAD) Status: NEW Severity: normal Priority: P2 Component: ld Assignee: unassigned at sourceware dot org Reporter: hjl.tools at gmail dot com Target Milestone: --- Target: i386,x86_64 "call *ld@TLSCALL(%rax)" calls _dl_tlsdesc_return which expects that RAX points to the TLS descriptor. Linker issues an error when there is TLS transition, but doesn't when there is no TLS transition: [hjl@gnu-cfl-3 tls-2]$ cat x.S .text .p2align 4 .globl get_ld .type get_ld, @function get_ld: .LFB0: .cfi_startproc subq$8, %rsp .cfi_def_cfa_offset 16 leaqld@TLSDESC(%rip), %rcx call*ld@TLSCALL(%rcx) addq%fs:0, %rax addq$8, %rsp .cfi_def_cfa_offset 8 ret .cfi_endproc .LFE0: .size get_ld, .-get_ld .section .note.GNU-stack,"",@progbits [hjl@gnu-cfl-3 tls-2]$ gcc -c x.S [hjl@gnu-cfl-3 tls-2]$ ld -shared x.o [hjl@gnu-cfl-3 tls-2]$ -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/31982] [2.43 Regression] mir 2.17 build failure during an LTO enabled build
https://sourceware.org/bugzilla/show_bug.cgi?id=31982 --- Comment #11 from H.J. Lu --- (In reply to Matthias Klose from comment #9) > Created attachment 15688 [details] > log of the build Does it fail on x86-64? -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/31982] [2.43 Regression] mir 2.17 build failure during an LTO enabled build
https://sourceware.org/bugzilla/show_bug.cgi?id=31982 --- Comment #12 from Matthias Klose --- sorry, I didn't mention the architectures. It fails on aarch64-linux-gnu, arm-linux-gnueabihf, arm-linux-gnueabi, alpha-linux-gnu, powerpc-linux-gnu and sparc64-linux-gnu. Other architectures work ok, see https://buildd.debian.org/status/package.php?p=mir -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/31982] [2.43 Regression] mir 2.17 build failure during an LTO enabled build
https://sourceware.org/bugzilla/show_bug.cgi?id=31982 --- Comment #13 from H.J. Lu --- (In reply to Matthias Klose from comment #12) > sorry, I didn't mention the architectures. It fails on aarch64-linux-gnu, > arm-linux-gnueabihf, arm-linux-gnueabi, alpha-linux-gnu, powerpc-linux-gnu > and sparc64-linux-gnu. Other architectures work ok, see > https://buildd.debian.org/status/package.php?p=mir Can you bisect which commit caused this? Some bugs may be only fixed on x86. If you have a self-contained test for aarch64-linux-gnu cross compiler, I can take a look. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/32123] Linker should check all invalid @TLSCALL usage
https://sourceware.org/bugzilla/show_bug.cgi?id=32123 Sam James changed: What|Removed |Added CC||sam at gentoo dot org See Also||https://sourceware.org/bugz ||illa/show_bug.cgi?id=32017, ||https://sourceware.org/bugz ||illa/show_bug.cgi?id=32022 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/32017] Linker failed to check invalid TLS sequence
https://sourceware.org/bugzilla/show_bug.cgi?id=32017 Sam James changed: What|Removed |Added See Also||https://sourceware.org/bugz ||illa/show_bug.cgi?id=32123 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/32022] Assembler shouldn't accept invalid TLS instructions
https://sourceware.org/bugzilla/show_bug.cgi?id=32022 Sam James changed: What|Removed |Added See Also||https://sourceware.org/bugz ||illa/show_bug.cgi?id=32123 -- You are receiving this mail because: You are on the CC list for the bug.
