public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/103324] RFE: Add a `make quickcheck` or `make smoketest` Makefile target to allow only running a portion of the testsuite
Date: Thu, 18 Nov 2021 23:51:42 +0000 [thread overview]
Message-ID: <bug-103324-4-uGqVaLbN8B@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103324-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103324
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2021-11-18
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Confirmed,
This what have been running since 2010 (and was there for a few years before
that):
cd check-check-dir; $(RUNTEST) TMPDIR=`pwd` --all --tools gcc
$(DGFLAGS) \
--srcdir=$(SRC)/gcc/testsuite execute.exp=20000112-1.c
This was for an out of tree already built toolchain testing even. If this
fails, I don't run the full testsuite. (this is not what I run for my upstream
testing though, only for my internal toolchain testing).
next prev parent reply other threads:[~2021-11-18 23:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 22:36 [Bug testsuite/103324] New: " egallager at gcc dot gnu.org
2021-11-18 23:51 ` pinskia at gcc dot gnu.org [this message]
2021-11-19 7:43 ` [Bug testsuite/103324] " rguenth at gcc dot gnu.org
2022-01-16 19:38 ` egallager at gcc dot gnu.org
2022-03-13 5:28 ` egallager at gcc dot gnu.org
2022-03-13 15:45 ` egallager at gcc dot gnu.org
2022-03-14 17:31 ` egallager at gcc dot gnu.org
2022-03-14 21:24 ` redi at gcc dot gnu.org
2022-05-29 6:16 ` sam at gentoo dot org
2023-08-12 14:48 ` egallager at gcc dot gnu.org
2023-10-16 2:14 ` egallager at gcc dot gnu.org
2023-10-16 4:53 ` egallager at gcc dot gnu.org
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-103324-4-uGqVaLbN8B@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).