public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-6515] testsuite: Support scanning tree-dumps Date: Tue, 7 Mar 2023 01:27:28 +0000 (GMT) [thread overview] Message-ID: <20230307012728.39C5F3858D39@sourceware.org> (raw) https://gcc.gnu.org/g:1690f928b379e8dac07832d25865ffe37d3c858b commit r13-6515-g1690f928b379e8dac07832d25865ffe37d3c858b Author: Hans-Peter Nilsson <hp@axis.com> Date: Fri Mar 3 21:18:05 2023 +0100 testsuite: Support scanning tree-dumps No planned usage. * lib/target-supports.exp (check_compile): Support scanning tree-dumps. Diff: --- gcc/testsuite/lib/target-supports.exp | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/gcc/testsuite/lib/target-supports.exp b/gcc/testsuite/lib/target-supports.exp index 4bad4dae582..a4fbc1998c7 100644 --- a/gcc/testsuite/lib/target-supports.exp +++ b/gcc/testsuite/lib/target-supports.exp @@ -87,6 +87,7 @@ proc check_compile {basename type contents args} { assembly { set output ${basename}[pid].s } object { set output ${basename}[pid].o } executable { set output ${basename}[pid].exe } + "tree-*" - "rtl-*" { set output ${basename}[pid].s lappend options "additional_flags=-fdump-$type" @@ -108,6 +109,9 @@ proc check_compile {basename type contents args} { if [regexp "rtl-(.*)" $type dummy rtl_type] { set scan_output "[glob $src.\[0-9\]\[0-9\]\[0-9\]r.$rtl_type]" file delete $output + } elseif [regexp "tree-(.*)" $type dummy tree_type] { + set scan_output "[glob $src.\[0-9\]\[0-9\]\[0-9\]t.$tree_type]" + file delete $output } # Restore additional_sources.
reply other threads:[~2023-03-07 1:27 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=20230307012728.39C5F3858D39@sourceware.org \ --to=hp@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).