From: Jonathan Wakely <jwakely@redhat.com>
To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: [committed 7/9] libstdc++: Remove redundant -std=gnu++17 options from containers tests
Date: Mon, 10 May 2021 16:29:52 +0100 [thread overview]
Message-ID: <20210510152952.GN3008@redhat.com> (raw)
In-Reply-To: <YJlQnPWJ/c47B+m0@redhat.com>
GCC defaults to -std=gnu++17 now anyway, and using it explicitly in the
dg-options directive prevents running these tests with different modes
such as -std=c++17 or -std=gnu++20.
Tested powerpc64le-linux. Committed to trunk.
next prev parent reply other threads:[~2021-05-10 15:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 15:26 [committed 1/9] libstdc++: Remove redundant -std=gnu++17 options from PSTL tests Jonathan Wakely
2021-05-10 15:27 ` [committed 2/9] libstdc++: Remove redundant -std=gnu++17 options from filesystem tests Jonathan Wakely
2021-05-10 15:27 ` [committed 3/9] libstdc++: Remove redundant -std=gnu++17 options from any/optional/variant tests Jonathan Wakely
2021-05-10 15:28 ` [committed 4/9] libstdc++: Remove redundant -std=gnu++17 options from concurrency tests Jonathan Wakely
2021-05-10 15:29 ` [committed 5/9] libstdc++: Remove redundant -std=gnu++17 options from PMR tests Jonathan Wakely
2021-05-10 15:29 ` [committed 6/9] libstdc++: Remove redundant -std=gnu++17 options from strings tests Jonathan Wakely
2021-05-10 15:29 ` Jonathan Wakely [this message]
2021-05-10 15:31 ` [committed 7/9] libstdc++: Remove redundant -std=gnu++17 options from containers tests Jonathan Wakely
2021-05-10 15:30 ` [committed 8/9] libstdc++: Remove redundant -std=gnu++17 options from algorithm tests Jonathan Wakely
2021-05-10 15:30 ` [committed 9/9] libstdc++: Remove redundant -std=gnu++17 options from remaining tests Jonathan Wakely
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=20210510152952.GN3008@redhat.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@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).