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 target/94711] New: [8/9/10 Regression] class with empty base passed incorrectly with -std=c++17 on arm
Date: Wed, 22 Apr 2020 12:12:14 +0000 [thread overview]
Message-ID: <bug-94711-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94711
Bug ID: 94711
Summary: [8/9/10 Regression] class with empty base passed
incorrectly with -std=c++17 on arm
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: ABI, wrong-code
Severity: blocker
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: jakub at gcc dot gnu.org
CC: jakub at gcc dot gnu.org, ktkachov at gcc dot gnu.org,
matmal01 at gcc dot gnu.org, mpolacek at gcc dot gnu.org,
rearnsha at gcc dot gnu.org, redi at gcc dot gnu.org,
rguenth at gcc dot gnu.org, rsandifo at gcc dot gnu.org
Depends on: 94383
Blocks: 94704, 94706, 94707
Target Milestone: ---
Target: aarch64-*-linux
+++ This bug was initially created as a clone of Bug #94383 +++
The same issue applies to 32-bit ARM too.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94383
[Bug 94383] [8/9/10 Regression] class with empty base passed incorrectly with
-std=c++17 on aarch64
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94704
[Bug 94704] [8/9/10 Regression] class with empty base passed incorrectly with
-std=c++17 on s390x/s390
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94706
[Bug 94706] [8/9/10 Regression] class with empty base passed incorrectly with
-std=c++17 on ia64
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94707
[Bug 94707] [8/9/10 Regression] class with empty base passed incorrectly with
-std=c++17 on powerpc64le
next reply other threads:[~2020-04-22 12:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 12:12 jakub at gcc dot gnu.org [this message]
2020-04-22 12:12 ` [Bug target/94711] " jakub at gcc dot gnu.org
2020-04-23 14:38 ` jakub at gcc dot gnu.org
2020-04-23 14:59 ` marxin at gcc dot gnu.org
2020-04-27 8:04 ` jakub at gcc dot gnu.org
2020-04-28 14:38 ` cvs-commit at gcc dot gnu.org
2020-04-28 14:44 ` matmal01 at gcc dot gnu.org
2020-04-28 14:45 ` matmal01 at gcc dot gnu.org
2021-11-05 23:18 ` timturnerc at yahoo 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-94711-4@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).