public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "y.gribov at samsung dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/59106] Failure to link against static libasan
Date: Wed, 13 Nov 2013 11:18:00 -0000 [thread overview]
Message-ID: <bug-59106-4-IPK1bniezy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59106-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59106
--- Comment #3 from Yury Gribov <y.gribov at samsung dot com> ---
(In reply to Kostya Serebryany from comment #2)
> We should be building libsanitizer with -fno-rtti
Ubsan seems to require it:
/home/ygribov/gcc/gcc-master/libsanitizer/ubsan/ubsan_type_hash.cc:121:63:
error: ‘dynamic_cast’ not permitted with -fno-rtti
dynamic_cast<const abi::__si_class_type_info*>(Derived))
^
>From gcc-bugs-return-434447-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Nov 13 11:20:19 2013
Return-Path: <gcc-bugs-return-434447-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13578 invoked by alias); 13 Nov 2013 11:20:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 13519 invoked by uid 48); 13 Nov 2013 11:20:15 -0000
From: "samsonov at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/59106] Failure to link against static libasan
Date: Wed, 13 Nov 2013 11:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: samsonov at google dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-59106-4-PeMn4revta@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-59106-4@http.gcc.gnu.org/bugzilla/>
References: <bug-59106-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2013-11/txt/msg01224.txt.bz2
Content-length: 529
http://gcc.gnu.org/bugzilla/show_bug.cgi?idY106
Alexey Samsonov <samsonov at google dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |samsonov at google dot com
--- Comment #4 from Alexey Samsonov <samsonov at google dot com> ---
Yeah, in LLVM/Clang we build C++-specific part of UBSan with -frtti (and link
it to C++ programs only), and the rest sanitizers with -fno-rtti.
next prev parent reply other threads:[~2013-11-13 11:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 9:26 [Bug sanitizer/59106] New: " y.gribov at samsung dot com
2013-11-13 9:34 ` [Bug sanitizer/59106] " y.gribov at samsung dot com
2013-11-13 9:39 ` kcc at gcc dot gnu.org
2013-11-13 11:18 ` y.gribov at samsung dot com [this message]
2013-11-13 11:24 ` kcc at gcc dot gnu.org
2013-11-13 11:53 ` y.gribov at samsung dot com
2013-11-13 11:57 ` kcc at gcc dot gnu.org
2013-11-13 12:02 ` jakub at gcc dot gnu.org
2013-11-13 12:38 ` kcc at gcc dot gnu.org
2013-11-13 12:39 ` y.gribov at samsung dot com
2013-11-15 12:47 ` kcc at gcc dot gnu.org
2013-11-15 12:53 ` y.gribov at samsung dot com
2013-11-15 13:30 ` kcc at gcc dot gnu.org
2013-11-18 6:49 ` y.gribov at samsung dot com
2013-11-18 7:19 ` kcc at gcc dot gnu.org
2013-11-18 7:39 ` jakub at gcc dot gnu.org
2013-11-18 8:03 ` ygribov at gcc dot gnu.org
2013-11-18 8:55 ` y.gribov at samsung dot com
2013-11-28 12:20 ` ygribov at gcc dot gnu.org
2013-11-28 12:22 ` y.gribov at samsung dot com
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-59106-4-IPK1bniezy@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: link
Be 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).