public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/104934] -fsanitize=undefined codegen err
Date: Tue, 15 Mar 2022 13:32:25 +0000	[thread overview]
Message-ID: <bug-104934-4-9M5u7glANN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104934-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104934

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
And the bug is?
The S class doesn't have the key method defined, so some other TU needs to
define it and thus provide the vtable and rtti for it.
Without -fsanitize=vptr the typeinfo isn't needed on this particular testcase
and the vtable isn't needed either, which is why you don't get an undefined
symbol in that case and you get it with -fsanitize=vptr or -fsanitize=undefined
that implies that.

  reply	other threads:[~2022-03-15 13:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-15 11:53 [Bug sanitizer/104934] New: " dimhen at gmail dot com
2022-03-15 13:32 ` jakub at gcc dot gnu.org [this message]
2022-03-15 16:14 ` [Bug sanitizer/104934] " dimhen at gmail dot com
2022-03-15 16:18 ` jakub 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-104934-4-9M5u7glANN@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).