public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/103240] std::type_info::before gives wrong answer for ARM EABI
Date: Tue, 23 Nov 2021 21:17:56 +0000	[thread overview]
Message-ID: <bug-103240-4-bLr39uHCMQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103240-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:

https://gcc.gnu.org/g:ec6ba81a038be488cec5e3bdc4f30b7876d9c5ea

commit r11-9270-gec6ba81a038be488cec5e3bdc4f30b7876d9c5ea
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Tue Nov 16 21:03:21 2021 +0000

    libstdc++: Fix std::type_info::before for ARM [PR103240]

    The r179236 fix for std::type_info::operator== should also have been
    applied to std::type_info::before. Otherwise two distinct types can
    compare equivalent due to using a string comparison, when they should do
    a pointer comparison.

    libstdc++-v3/ChangeLog:

            PR libstdc++/103240
            * libsupc++/tinfo2.cc (type_info::before): Use unadjusted name
            to check for the '*' prefix.
            * testsuite/util/testsuite_shared.cc: Add type_info object for
            use in new test.
            * testsuite/18_support/type_info/103240.cc: New test.

    (cherry picked from commit 054bf99841aad3869c70643b2ba2d9f85770c980)

  parent reply	other threads:[~2021-11-23 21:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-15  0:20 [Bug libstdc++/103240] New: " redi at gcc dot gnu.org
2021-11-15  0:21 ` [Bug libstdc++/103240] " redi at gcc dot gnu.org
2021-11-15  0:36 ` redi at gcc dot gnu.org
2021-11-17 17:22 ` cvs-commit at gcc dot gnu.org
2021-11-17 17:42 ` redi at gcc dot gnu.org
2021-11-23 21:17 ` cvs-commit at gcc dot gnu.org [this message]
2023-04-29 16:15 ` frankhb1989 at gmail dot com
2023-04-29 18:01 ` frankhb1989 at gmail dot com
2023-05-02 16:56 ` redi at gcc dot gnu.org
2023-05-04 10:31 ` frankhb1989 at gmail dot com
2023-05-04 11:04 ` redi at gcc dot gnu.org
2023-05-05 16:28 ` frankhb1989 at gmail 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-103240-4-bLr39uHCMQ@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).