public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/53222] New: dejagnu trims leading whitespace Date: Thu, 03 May 2012 22:39:00 -0000 [thread overview] Message-ID: <bug-53222-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53222 Bug #: 53222 Summary: dejagnu trims leading whitespace Classification: Unclassified Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: testsuite AssignedTo: unassigned@gcc.gnu.org ReportedBy: manu@gcc.gnu.org This patch should still allow us to prune all caret diagnostics, since they always start with whitespace: Index: libstdc++-v3/testsuite/lib/prune.exp =================================================================== --- libstdc++-v3/testsuite/lib/prune.exp (revision 187039) +++ libstdc++-v3/testsuite/lib/prune.exp (working copy) @@ -34,11 +34,11 @@ proc libstdc++-dg-prune { system text } # send_user "Before:$text\n" # Ignore caret diagnostics. Unfortunately dejaGNU trims leading # spaces, so one cannot rely on them being present. - regsub -all "(^|\n)\[^\n\]+\n *\\^\n" $text "\n" text + regsub -all "(^ |\n )\[^\n\]+\n *\\^\n" $text "\n" text # Cygwin warns about -ffunction-sections regsub -all "(^|\n)\[^\n\]*: -ffunction-sections may affect debugging on some targets\[^\n\]*" $text "" text # Remove parts of warnings that refer to location of previous However, DejaGNU seems to trim leading whitespace: /home/manuel/test2/src/libstdc++-v3/testsuite/17_intro/using_namespace_std_tr1_neg.cc:66:27: error: expected namespace-name before ';' token^M using namespace std::tr1; // { dg-error "is not a namespace-name" }^M ^^M PASS: 17_intro/using_namespace_std_tr1_neg.cc (test for errors, line 66) PASS: 17_intro/using_namespace_std_tr1_neg.cc (test for errors, line 66) FAIL: 17_intro/using_namespace_std_tr1_neg.cc (test for excess errors) Excess errors: using namespace std::tr1; // { dg-error "is not a namespace-name" } ^ This is unfortunate, because it makes quite hard to match any arbitrary output.
next reply other threads:[~2012-05-03 22:39 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-03 22:39 manu at gcc dot gnu.org [this message] 2013-04-19 7:29 ` [Bug testsuite/53222] " skannan at redhat dot com 2013-04-19 7:51 ` manu 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-53222-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: 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).