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/94706] [8/9/10 Regression] class with empty base passed incorrectly with -std=c++17 on ia64
Date: Wed, 22 Apr 2020 07:10:17 +0000 [thread overview]
Message-ID: <bug-94706-4-tn7xwgk8Ul@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94706-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94706
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |schwab at gcc dot gnu.org
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Andreas, do you think you could find out which struct (at least one) FAILs?
See above...
next prev parent reply other threads:[~2020-04-22 7:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 7:09 [Bug target/94706] New: " jakub at gcc dot gnu.org
2020-04-22 7:10 ` jakub at gcc dot gnu.org [this message]
2020-04-22 7:36 ` [Bug target/94706] " rguenth at gcc dot gnu.org
2020-04-22 9:08 ` schwab@linux-m68k.org
2020-04-22 9:09 ` schwab@linux-m68k.org
2020-04-22 9:16 ` schwab@linux-m68k.org
2020-04-22 9:16 ` schwab@linux-m68k.org
2020-04-22 9:20 ` schwab@linux-m68k.org
2020-04-22 9:21 ` schwab@linux-m68k.org
2020-04-22 9:23 ` schwab@linux-m68k.org
2020-04-22 9:24 ` schwab@linux-m68k.org
2020-04-22 9:27 ` schwab@linux-m68k.org
2020-04-22 9:27 ` schwab@linux-m68k.org
2020-04-22 9:30 ` schwab@linux-m68k.org
2020-04-22 9:30 ` schwab@linux-m68k.org
2020-04-22 9:34 ` schwab@linux-m68k.org
2020-04-22 9:35 ` schwab@linux-m68k.org
2020-04-22 10:54 ` jakub at gcc dot gnu.org
2020-04-22 12:11 ` jakub at gcc dot gnu.org
2020-04-22 12:20 ` schwab@linux-m68k.org
2020-04-22 14:48 ` cvs-commit at gcc dot gnu.org
2020-04-23 14:38 ` jakub at gcc dot gnu.org
2020-04-29 7:08 ` cvs-commit at gcc dot gnu.org
2020-05-07 9:22 ` [Bug target/94706] [8/9/10/11 " jakub 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-94706-4-tn7xwgk8Ul@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).