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 target/94383] [8/9/10 Regression] class with empty base passed incorrectly with -std=c++17 on aarch64
Date: Fri, 24 Apr 2020 17:15:09 +0000 [thread overview]
Message-ID: <bug-94383-4-qtAGt0ZnyL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94383-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94383
--- Comment #17 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:9407f0c32b215d55d3474a234b0043bddc185b1c
commit r10-7948-g9407f0c32b215d55d3474a234b0043bddc185b1c
Author: Jakub Jelinek <jakub@redhat.com>
Date: Fri Apr 24 19:14:27 2020 +0200
testsuite: C++14 vs. C++17 struct-layout-1.exp testing with
ALT_CXX_UNDER_TEST [PR94383]
> I haven't added (yet) checks if the alternate compiler does support these
> options (I think that can be done incrementally), so for now this testing
is
> done only if the alternate compiler is not used.
This patch does that, so now when testing against not too old compiler
it can do the -std=c++14 vs. -std=c++17 testing also between under test and
alt compilers.
2020-04-24 Jakub Jelinek <jakub@redhat.com>
PR c++/94383
* g++.dg/compat/struct-layout-1.exp: Use the -std=c++14 vs.
-std=c++17
ABI compatibility testing even with ALT_CXX_UNDER_TEST, as long as
that compiler accepts -std=c++14 and -std=c++17 options.
next prev parent reply other threads:[~2020-04-24 17:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-28 15:54 [Bug target/94383] New: [8/9/10 Regression] class with empty base passed incorrectly with -std=c++17 redi at gcc dot gnu.org
2020-03-28 15:55 ` [Bug target/94383] " redi at gcc dot gnu.org
2020-03-28 16:01 ` redi at gcc dot gnu.org
2020-03-28 17:37 ` [Bug target/94383] [8/9/10 Regression] class with empty base passed incorrectly with -std=c++17 on aarch64 redi at gcc dot gnu.org
2020-03-28 17:39 ` redi at gcc dot gnu.org
2020-03-28 18:00 ` mpolacek at gcc dot gnu.org
2020-03-28 19:26 ` pinskia at gcc dot gnu.org
2020-03-30 8:13 ` rguenth at gcc dot gnu.org
2020-03-30 14:04 ` jakub at gcc dot gnu.org
2020-03-30 14:38 ` jakub at gcc dot gnu.org
2020-04-15 15:38 ` jakub at gcc dot gnu.org
2020-04-16 14:08 ` matmal01 at gcc dot gnu.org
2020-04-16 14:14 ` jakub at gcc dot gnu.org
2020-04-20 18:21 ` jakub at gcc dot gnu.org
2020-04-21 15:10 ` cvs-commit at gcc dot gnu.org
2020-04-22 12:10 ` jakub at gcc dot gnu.org
2020-04-22 14:47 ` cvs-commit at gcc dot gnu.org
2020-04-23 14:34 ` cvs-commit at gcc dot gnu.org
2020-04-23 14:38 ` jakub at gcc dot gnu.org
2020-04-23 16:54 ` redi at gcc dot gnu.org
2020-04-24 17:15 ` cvs-commit at gcc dot gnu.org [this message]
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-94383-4-qtAGt0ZnyL@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).