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 c++/100797] [10/11 Regression] using declaration causing virtual call with wrongly adjusted this pointer Date: Tue, 01 Jun 2021 15:53:43 +0000 [thread overview] Message-ID: <bug-100797-4-2xaVdfqDhI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100797-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100797 --- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:1027e8c8837d9d4933946f2888d85deef2cf850b commit r10-9876-g1027e8c8837d9d4933946f2888d85deef2cf850b Author: Jason Merrill <jason@redhat.com> Date: Thu May 27 23:54:52 2021 -0400 c++: 'this' adjustment for devirtualized call My patch for 95719 made us do a better job of finding the actual virtual function we want to call, but didn't update the 'this' pointer adjustment to match. This backport also incorporates a bit of the r11-1638 reorganization. PR c++/100797 PR c++/95719 gcc/cp/ChangeLog: * call.c (build_over_call): Adjust base_binfo in resolves_to_fixed_type_p case. gcc/testsuite/ChangeLog: * g++.dg/inherit/virtual15.C: New test. * g++.dg/inherit/virtual15a.C: New test.
next prev parent reply other threads:[~2021-06-01 15:53 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-27 10:37 [Bug c++/100797] New: " sbergman at redhat dot com 2021-05-27 16:23 ` [Bug c++/100797] [9/10/11/12 Regression] " ppalka at gcc dot gnu.org 2021-05-27 16:25 ` ppalka at gcc dot gnu.org 2021-05-28 3:24 ` jason at gcc dot gnu.org 2021-05-28 9:23 ` cvs-commit at gcc dot gnu.org 2021-05-28 10:42 ` [Bug c++/100797] [10/11/12 " rguenth at gcc dot gnu.org 2021-05-28 12:58 ` cvs-commit at gcc dot gnu.org 2021-05-28 13:04 ` jason at gcc dot gnu.org 2021-05-31 6:26 ` sbergman at redhat dot com 2021-06-01 8:21 ` rguenth at gcc dot gnu.org 2021-06-01 8:43 ` [Bug c++/100797] [10/11 " rguenth at gcc dot gnu.org 2021-06-01 15:53 ` cvs-commit at gcc dot gnu.org 2021-06-01 15:53 ` cvs-commit at gcc dot gnu.org [this message] 2021-06-01 19:16 ` jason 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-100797-4-2xaVdfqDhI@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).