public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/101749] gcc -static-libasan broken because libasan.a needs __cxa_guard_release in libstdc++ Date: Thu, 05 Aug 2021 08:51:58 +0000 [thread overview] Message-ID: <bug-101749-4-owWhy9gK2v@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101749-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101749 --- Comment #13 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-9 branch has been updated by Martin Liska <marxin@gcc.gnu.org>: https://gcc.gnu.org/g:11e2ac8f75060d9be432e8db1f358298a75c98d4 commit r9-9661-g11e2ac8f75060d9be432e8db1f358298a75c98d4 Author: Martin Liska <mliska@suse.cz> Date: Thu Aug 5 10:43:17 2021 +0200 sanitizer: cherry pick 414482751452e54710f16bae58458c66298aaf69 The patch is needed in order to support recent glibc (2.34). libsanitizer/ChangeLog: PR sanitizer/101749 * sanitizer_common/sanitizer_posix_libcdep.cc: Prevent generation of dependency on _cxa_guard for static initialization.
next prev parent reply other threads:[~2021-08-05 8:51 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-03 12:23 [Bug sanitizer/101749] New: " xry111 at mengyan1223 dot wang 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 [this message] 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-owWhy9gK2v@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).