public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/111390] New: 'make check-compile' target is not useful
Date: Tue, 12 Sep 2023 16:25:38 +0000 [thread overview]
Message-ID: <bug-111390-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111390
Bug ID: 111390
Summary: 'make check-compile' target is not useful
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: redi at gcc dot gnu.org
Target Milestone: ---
This makefile target does compilation-only testing, to check that tests can be
built. But there's no parallelism, so it takes ages. Worse, it ignores dejagnu
directives so just runs everything with a default set of options, including the
implicit -std=gnu++17
This means that all C++20 and later tests fail. And any XFAIL tests with
dg-error directives "fail" noisily.
I'm not sure it is useful to keep it.
If we want to do compilation-only testing, I think it would be better to modify
the dejagnu procs so that "do-do run" tests are treated as "dg-do compile".
next reply other threads:[~2023-09-12 16:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 16:25 redi at gcc dot gnu.org [this message]
2023-09-12 19:06 ` [Bug libstdc++/111390] " egallager at gcc dot gnu.org
2023-09-12 20:10 ` redi at gcc dot gnu.org
2023-09-13 0:13 ` egallager at gcc dot gnu.org
2023-09-13 0:29 ` redi at gcc dot gnu.org
2023-09-13 7:02 ` rguenth at gcc dot gnu.org
2023-09-13 7:18 ` [Bug libstdc++/111390] libstdc++-v3/scripts/check_compile script " redi at gcc dot gnu.org
2023-09-13 14:31 ` joseph at codesourcery 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-111390-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).