public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "xry111 at mengyan1223 dot wang" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/101749] New: gcc -static-libasan broken because libasan.a needs __cxa_guard_release in libstdc++ Date: Tue, 03 Aug 2021 12:23:25 +0000 [thread overview] Message-ID: <bug-101749-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101749 Bug ID: 101749 Summary: gcc -static-libasan broken because libasan.a needs __cxa_guard_release in libstdc++ Product: gcc Version: 11.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: xry111 at mengyan1223 dot wang CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at gcc dot gnu.org Target Milestone: --- Test summary: FAIL: c-c++-common/asan/pr59063-2.c -O0 (test for excess errors) UNRESOLVED: c-c++-common/asan/pr59063-2.c -O0 compilation failed to produce executable FAIL: c-c++-common/asan/pr59063-2.c -O1 (test for excess errors) UNRESOLVED: c-c++-common/asan/pr59063-2.c -O1 compilation failed to produce executable FAIL: c-c++-common/asan/pr59063-2.c -O2 (test for excess errors) UNRESOLVED: c-c++-common/asan/pr59063-2.c -O2 compilation failed to produce executable FAIL: c-c++-common/asan/pr59063-2.c -O3 -g (test for excess errors) UNRESOLVED: c-c++-common/asan/pr59063-2.c -O3 -g compilation failed to produce executable FAIL: c-c++-common/asan/pr59063-2.c -Os (test for excess errors) UNRESOLVED: c-c++-common/asan/pr59063-2.c -Os compilation failed to produce executable FAIL: c-c++-common/asan/pr59063-2.c -O2 -flto -fno-use-linker-plugin -flto-partition=none (test for excess errors) UNRESOLVED: c-c++-common/asan/pr59063-2.c -O2 -flto -fno-use-linker-plugin -flto-partition=none compilation failed to produce executable FAIL: c-c++-common/asan/pr59063-2.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects (test for excess errors) UNRESOLVED: c-c++-common/asan/pr59063-2.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects compilation failed to produce executable $ cc dummy.c -fsanitize=address -static-libasan /usr/bin/ld: /usr/lib/gcc/x86_64-pc-linux-gnu/11.2.0/../../../../lib/libasan.a(sanitizer_posix_libcdep.o): in function `__sanitizer::SetAlternateSignalStack()': /sources/gcc-11.2.0/build/x86_64-pc-linux-gnu/libsanitizer/sanitizer_common/../../../../libsanitizer/sanitizer_common/sanitizer_posix_libcdep.cpp:170: undefined reference to `__cxa_guard_acquire' /usr/bin/ld: /usr/lib/gcc/x86_64-pc-linux-gnu/11.2.0/../../../../lib/libasan.a(sanitizer_posix_libcdep.o): in function `GetAltStackSize': /sources/gcc-11.2.0/build/x86_64-pc-linux-gnu/libsanitizer/sanitizer_common/../../../../libsanitizer/sanitizer_common/sanitizer_posix_libcdep.cpp:170: undefined reference to `__cxa_guard_release' /usr/bin/ld: /usr/lib/gcc/x86_64-pc-linux-gnu/11.2.0/../../../../lib/libasan.a(sanitizer_posix_libcdep.o): in function `__sanitizer::UnsetAlternateSignalStack()': /sources/gcc-11.2.0/build/x86_64-pc-linux-gnu/libsanitizer/sanitizer_common/../../../../libsanitizer/sanitizer_common/sanitizer_posix_libcdep.cpp:170: undefined reference to `__cxa_guard_acquire' /usr/bin/ld: /usr/lib/gcc/x86_64-pc-linux-gnu/11.2.0/../../../../lib/libasan.a(sanitizer_posix_libcdep.o): in function `GetAltStackSize': /sources/gcc-11.2.0/build/x86_64-pc-linux-gnu/libsanitizer/sanitizer_common/../../../../libsanitizer/sanitizer_common/sanitizer_posix_libcdep.cpp:170: undefined reference to `__cxa_guard_release' collect2: error: ld returned 1 exit status Not sure if this is because something has changed in glibc-2.34.
next reply other threads:[~2021-08-03 12:23 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-03 12:23 xry111 at mengyan1223 dot wang [this message] 2021-08-03 12:29 ` [Bug sanitizer/101749] " marxin at gcc dot gnu.org 2021-08-03 12:32 ` xry111 at mengyan1223 dot wang 2021-08-03 12:57 ` rguenth at gcc dot gnu.org 2021-08-03 13:08 ` xry111 at mengyan1223 dot wang 2021-08-03 13:10 ` xry111 at mengyan1223 dot wang 2021-08-03 16:15 ` redi at gcc dot gnu.org 2021-08-04 8:08 ` marxin at gcc dot gnu.org 2021-08-04 9:00 ` jakub at gcc dot gnu.org 2021-08-04 15:31 ` marxin at gcc dot gnu.org 2021-08-04 15:34 ` jakub at gcc dot gnu.org 2021-08-04 15:36 ` marxin at gcc dot gnu.org 2021-08-05 8:48 ` cvs-commit at gcc dot gnu.org 2021-08-05 8:49 ` cvs-commit at gcc dot gnu.org 2021-08-05 8:51 ` cvs-commit at gcc dot gnu.org 2021-08-05 8:52 ` marxin at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-101749-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).