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] 'make check-compile' target is not useful Date: Wed, 13 Sep 2023 00:29:50 +0000 [thread overview] Message-ID: <bug-111390-4-SWm7tGbanI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111390-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111390 --- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> --- I think what you're describing or looking for is something completely different, which might be useful but is not what is present today. The libstdc++-v3/scripts/check_compile script cannot be turned into what you're describing. There's simply no way to get to what you want from a naive shell script that isn't parallelized, and doesn't understand the dg-* directives in the tests, and only supports a single -std option for all tests. What we have today is not useful. A replacement would have to be written from scratch anyway, so ripping it out entirely has no downside as far as I can see.
next prev parent reply other threads:[~2023-09-13 0:29 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-12 16:25 [Bug libstdc++/111390] New: " redi at gcc dot gnu.org 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 [this message] 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-SWm7tGbanI@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: linkBe 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).