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++/104139] [12 Regression] g++.dg/abi/no_unique_address2.C at r12-6028 (a37e8ce3b663) Date: Fri, 21 Jan 2022 17:06:47 +0000 [thread overview] Message-ID: <bug-104139-4-czBT78ZHm9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104139-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104139 --- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:23be9f83bbd2c6f03580757adbfe599de6bf702b commit r12-6800-g23be9f83bbd2c6f03580757adbfe599de6bf702b Author: Jason Merrill <jason@redhat.com> Date: Fri Jan 21 11:16:49 2022 -0500 c++: [[no_unique_address]] and virtual base [PR104139] Fixing a thinko in my patch for 103681: when computing the size of a virtual base, it would help to use its binfo instead of the one for the derived class. PR c++/104139 PR c++/103681 gcc/cp/ChangeLog: * class.cc (end_of_class): Use base_binfo. gcc/testsuite/ChangeLog: * g++.dg/abi/no_unique_address2.C: Adjust to detect this on x86-64.
next prev parent reply other threads:[~2022-01-21 17:06 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-20 4:47 [Bug c++/104139] New: " hp at gcc dot gnu.org 2022-01-20 4:53 ` [Bug c++/104139] " hp at gcc dot gnu.org 2022-01-20 8:02 ` rguenth at gcc dot gnu.org 2022-01-21 1:22 ` hp at gcc dot gnu.org 2022-01-21 2:09 ` jason at gcc dot gnu.org 2022-01-21 17:06 ` cvs-commit at gcc dot gnu.org [this message] 2022-01-21 20:19 ` 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-104139-4-czBT78ZHm9@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).