public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Marek Polacek <mpolacek@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r14-10075] testsuite: prune -freport-bug output Date: Mon, 22 Apr 2024 15:26:13 +0000 (GMT) [thread overview] Message-ID: <20240422152613.D1D1C3858D35@sourceware.org> (raw) https://gcc.gnu.org/g:0db19228a9feba5a8f4e13b21f25f3aa8a6c5e85 commit r14-10075-g0db19228a9feba5a8f4e13b21f25f3aa8a6c5e85 Author: Marek Polacek <polacek@redhat.com> Date: Fri Apr 19 13:51:41 2024 -0400 testsuite: prune -freport-bug output When the compiler defaults to -freport-bug, a few dg-ice tests fail with: Excess errors: Preprocessed source stored into /tmp/cc6hldZ0.out file, please attach this to your bugreport. We could add -fno-report-bug to those tests. But it seems to me that a better fix would be to prune the "Preprocessed source stored..." message in prune_gcc_output. gcc/testsuite/ChangeLog: * lib/prune.exp (prune_gcc_output): Also prune -freport-bug output. Reviewed-by: Jakub Jelinek <jakub@redhat.com> Diff: --- gcc/testsuite/lib/prune.exp | 1 + 1 file changed, 1 insertion(+) diff --git a/gcc/testsuite/lib/prune.exp b/gcc/testsuite/lib/prune.exp index f3d3c99fbcb..d00d37f015f 100644 --- a/gcc/testsuite/lib/prune.exp +++ b/gcc/testsuite/lib/prune.exp @@ -51,6 +51,7 @@ proc prune_gcc_output { text } { regsub -all "(^|\n)\[^\n\]*: re(compiling|linking)\[^\n\]*" $text "" text regsub -all "(^|\n)Please submit.*instructions\[^\n\]*" $text "" text regsub -all "(^|\n)\[0-9\]\[0-9\]* errors\." $text "" text + regsub -all "(^|\n)Preprocessed.*bugreport\[^\n\]*" $text "" text # Diagnostic inclusion stack regsub -all "(^|\n)(In file)?\[ \]+included from \[^\n\]*" $text "" text
reply other threads:[~2024-04-22 15:26 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240422152613.D1D1C3858D35@sourceware.org \ --to=mpolacek@gcc.gnu.org \ --cc=gcc-cvs@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).