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 libstdc++/103453] ASAN detection with clang Date: Tue, 30 Nov 2021 20:11:18 +0000 [thread overview] Message-ID: <bug-103453-4-P1rt0KfJbT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103453-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103453 --- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:cca6090b13ab503bef1cfa327e2d107789d6bd30 commit r12-5636-gcca6090b13ab503bef1cfa327e2d107789d6bd30 Author: Jonathan Wakely <jwakely@redhat.com> Date: Tue Nov 30 13:14:38 2021 +0000 libstdc++: Make Asan detection work for Clang [PR103453] Clang doesn't define __SANITIZE_ADDRESS__ so use its __has_feature check to detect Asan instead. libstdc++-v3/ChangeLog: PR libstdc++/103453 * config/allocator/malloc_allocator_base.h (_GLIBCXX_SANITIZE_STD_ALLOCATOR): Define for Clang. * config/allocator/new_allocator_base.h (_GLIBCXX_SANITIZE_STD_ALLOCATOR): Likewise.
next prev parent reply other threads:[~2021-11-30 20:11 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-27 19:03 [Bug libstdc++/103453] New: " glisse at gcc dot gnu.org 2021-11-27 23:33 ` [Bug libstdc++/103453] " redi at gcc dot gnu.org 2021-11-30 0:21 ` pinskia at gcc dot gnu.org 2021-11-30 13:52 ` redi at gcc dot gnu.org 2021-11-30 20:11 ` cvs-commit at gcc dot gnu.org [this message] 2021-11-30 20:18 ` redi at gcc dot gnu.org 2021-12-01 1:01 ` unlvsur at live dot com 2021-12-01 1:02 ` unlvsur at live dot com 2021-12-01 1:06 ` unlvsur at live dot com 2021-12-01 1:22 ` unlvsur at live dot com 2021-12-01 4:51 ` unlvsur at live dot com 2021-12-01 8:29 ` redi at gcc dot gnu.org 2021-12-01 8:37 ` redi at gcc dot gnu.org 2022-01-05 22:06 ` cvs-commit at gcc dot gnu.org 2022-01-05 22:06 ` cvs-commit at gcc dot gnu.org 2022-01-05 22:10 ` redi 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-103453-4-P1rt0KfJbT@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).