From: "Koning, Paul" <Paul.Koning@dell.com>
To: GCC Development <gcc@gcc.gnu.org>
Subject: Setting test suite not to try debug output cases
Date: Fri, 2 Sep 2022 18:55:57 +0000 [thread overview]
Message-ID: <C36B0E9C-1BC1-4A57-B7D0-0790486AFF30@dell.com> (raw)
Given that pdp11 no longer supports debug output, I get a lot more test failures, like this:
spawn -ignore SIGHUP /Users/pkoning/Documents/svn/build/pdp/gcc/xgcc -B/Users/pkoning/Documents/svn/build/pdp/gcc/ -mlra -fdiagnostics-plain-output -Og -g -w -c -o 20000105-1.o /Users/pkoning/Documents/svn/gcc/gcc/testsuite/gcc.c-torture/compile/20000105-1.c
xgcc: warning: target system does not support debug output
cc1: warning: target system does not support debug output
FAIL: gcc.c-torture/compile/20000105-1.c -Og -g (test for excess errors)
I assume there is some way in the test suite machinery to globally skip all "debug output" cases. How would I do that?
paul
next reply other threads:[~2022-09-02 18:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 18:55 Koning, Paul [this message]
2022-09-05 9:29 ` Richard Biener
2022-09-05 12:23 ` Koning, Paul
2022-09-05 12:27 ` Richard Biener
2022-09-05 12:29 ` Iain Sandoe
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=C36B0E9C-1BC1-4A57-B7D0-0790486AFF30@dell.com \
--to=paul.koning@dell.com \
--cc=gcc@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).