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/94325] [8/9 Regression] UBSAN: "invalid vptr" false positive for virtual inheritance with -fno-sanitize-recover=all Date: Wed, 08 Apr 2020 13:33:26 +0000 [thread overview] Message-ID: <bug-94325-4-7kZ6UWlpgT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94325-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94325 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org Summary|[8/9/10 Regression] UBSAN: |[8/9 Regression] UBSAN: |"invalid vptr" false |"invalid vptr" false |positive for virtual |positive for virtual |inheritance with |inheritance with |-fno-sanitize-recover=all |-fno-sanitize-recover=all Status|NEW |ASSIGNED --- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Fixed on the trunk so far.
next prev parent reply other threads:[~2020-04-08 13:33 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-25 12:56 [Bug c++/94325] New: [UBSAN] " jaroslaw.melzer.gcc at gmail dot com 2020-03-25 13:09 ` [Bug sanitizer/94325] " marxin at gcc dot gnu.org 2020-03-25 13:58 ` [Bug sanitizer/94325] [8/9/10 Regression] UBSAN: " marxin at gcc dot gnu.org 2020-04-01 9:00 ` rguenth at gcc dot gnu.org 2020-04-06 11:27 ` jakub at gcc dot gnu.org 2020-04-06 11:41 ` jakub at gcc dot gnu.org 2020-04-08 13:31 ` cvs-commit at gcc dot gnu.org 2020-04-08 13:33 ` jakub at gcc dot gnu.org [this message] 2020-09-16 19:20 ` [Bug sanitizer/94325] [8/9 " cvs-commit at gcc dot gnu.org 2020-09-17 17:22 ` 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-94325-4-7kZ6UWlpgT@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).