From: Richard Sandiford <richard.sandiford@arm.com>
To: Tamar Christina <tamar.christina@arm.com>
Cc: gcc-patches@gcc.gnu.org, nd@arm.com
Subject: Re: [PATCH][testsuite]: make check-functions-body dump expected and seen cases on failure.
Date: Fri, 23 Sep 2022 10:32:16 +0100 [thread overview]
Message-ID: <mptczbm1lnj.fsf@arm.com> (raw)
In-Reply-To: <patch-16250-tamar@arm.com> (Tamar Christina's message of "Fri, 23 Sep 2022 10:23:03 +0100")
Tamar Christina <tamar.christina@arm.com> writes:
> Hi All,
>
> Often times when a check_function_body check fails it can be quite hard to
> figure out why as no additional information is provided.
>
> This changes it so that on failures it prints out the regex expression it's
> using and the text it's comparing against to the verbose log.
>
> This makes it much easier to figure out why a test has failed.
>
> Bootstrapped Regtested on aarch64-none-linux-gnu and no issues.
>
> Ok for master?
>
> Thanks,
> Tamar
>
> gcc/testsuite/ChangeLog:
>
> * lib/scanasm.exp (check_function_body): Add debug output to verbose log
> on failure.
OK, thanks.
Richard
>
> --- inline copy of patch --
> diff --git a/gcc/testsuite/lib/scanasm.exp b/gcc/testsuite/lib/scanasm.exp
> index a80630bb2a819812ce1fe05184535011a12f1288..7c9dcfc9b2e49093355219f76838161f4c3302df 100644
> --- a/gcc/testsuite/lib/scanasm.exp
> +++ b/gcc/testsuite/lib/scanasm.exp
> @@ -803,7 +803,12 @@ proc check_function_body { functions name body_regexp } {
> if { ![info exists up_functions($name)] } {
> return 0
> }
> - return [regexp "^$body_regexp\$" $up_functions($name)]
> + set fn_res [regexp "^$body_regexp\$" $up_functions($name)]
> + if { !$fn_res } {
> + verbose -log "body: $body_regexp"
> + verbose -log "against: $up_functions($name)"
> + }
> + return $fn_res
> }
>
> # Check the implementations of functions against expected output. Used as:
prev parent reply other threads:[~2022-09-23 9:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 9:23 Tamar Christina
2022-09-23 9:32 ` Richard Sandiford [this message]
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=mptczbm1lnj.fsf@arm.com \
--to=richard.sandiford@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nd@arm.com \
--cc=tamar.christina@arm.com \
/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).