public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakob2811 at hotmail dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/105387] libstdc++: with -fno-rtti, pointer type info class incorrectly matches non-pointer type info classes
Date: Thu, 28 Apr 2022 01:57:16 +0000	[thread overview]
Message-ID: <bug-105387-4-Jz2Ed7ehe8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105387-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Jakob Hasse <jakob2811 at hotmail dot de> ---
Thanks for the kind feedback!

I think I do have a test case now, using placement new to control the memory
adjacent to the type object. My patch seems to fix it. Right now I'm working on
integrating it into the test suite.

  parent reply	other threads:[~2022-04-28  1:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-26  8:58 [Bug c++/105387] New: " jakob2811 at hotmail dot de
2022-04-26  9:03 ` [Bug c++/105387] " rguenth at gcc dot gnu.org
2022-04-26  9:07 ` jakub at gcc dot gnu.org
2022-04-28  1:57 ` jakob2811 at hotmail dot de [this message]
2022-05-04 22:18 ` [Bug libstdc++/105387] " redi at gcc dot gnu.org
2022-11-05 14:03 ` cvs-commit at gcc dot gnu.org
2022-11-05 14:05 ` 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-105387-4-Jz2Ed7ehe8@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).