public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/64670] -fsanitize=vptr leads to "undefined reference to `typeinfo for class'" Date: Mon, 09 Feb 2015 22:00:00 -0000 [thread overview] Message-ID: <bug-64670-4-4dy9eex34o@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64670-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64670 --- Comment #8 from Jason Merrill <jason at gcc dot gnu.org> --- (In reply to Tobias Burnus from comment #5) > Updated test case (part 1/2): [main file] compile with g++ -fsanitize=vptr In this test case you have > #pragma implementation "test.h" followed by > # 1 "test2.h" 1 > #pragma interface so the #pragma implementation doesn't match. If I change it to be "test2.h" I get the typeinfo for LogListener.
next prev parent reply other threads:[~2015-02-09 22:00 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-19 15:32 [Bug sanitizer/64670] New: " burnus at gcc dot gnu.org 2015-01-19 15:58 ` [Bug sanitizer/64670] " burnus at gcc dot gnu.org 2015-01-19 16:07 ` mpolacek at gcc dot gnu.org 2015-01-19 16:14 ` jakub at gcc dot gnu.org 2015-01-29 15:52 ` jason at gcc dot gnu.org 2015-01-30 13:15 ` burnus at gcc dot gnu.org 2015-02-09 16:42 ` burnus at gcc dot gnu.org 2015-02-09 22:00 ` jason at gcc dot gnu.org [this message] 2015-02-10 8:09 ` burnus at gcc dot gnu.org 2015-02-10 16:23 ` jason at gcc dot gnu.org 2015-02-10 16:26 ` burnus at gcc dot gnu.org 2015-02-10 16:32 ` jason at gcc dot gnu.org 2015-02-10 16:50 ` burnus 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-64670-4-4dy9eex34o@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).