From: Mike Stump <mikestump@comcast.net>
To: Hans-Peter Nilsson <hp@axis.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] testsuite: Support scanning tree-dumps
Date: Mon, 6 Mar 2023 13:17:40 -0800 [thread overview]
Message-ID: <0CAFE790-96B2-4BBD-922B-DFB65D4AD34C@comcast.net> (raw)
In-Reply-To: <20230306185255.721FC20405@pchp3.se.axis.com>
On Mar 6, 2023, at 10:52 AM, Hans-Peter Nilsson via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
>
> Ok to apply?
Ok.
> * lib/target-supports.exp (check_compile): Support scanning tree-dumps.
next prev parent reply other threads:[~2023-03-06 21:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 18:45 [PATCH 1/3] testsuite: Add tail_call effective target Hans-Peter Nilsson
2023-03-06 18:47 ` [PATCH 2/3] doc: Document testsuite check_effective_target_tail_call Hans-Peter Nilsson
2023-03-06 18:50 ` [PATCH 3/3] testsuite: Gate gcc.dg/plugin/must-tail-call-1.c and -2.c on tail_call Hans-Peter Nilsson
2023-03-06 18:52 ` [PATCH] testsuite: Support scanning tree-dumps Hans-Peter Nilsson
2023-03-06 21:17 ` Mike Stump [this message]
2023-03-06 21:14 ` [PATCH 1/3] testsuite: Add tail_call effective target Mike Stump
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=0CAFE790-96B2-4BBD-922B-DFB65D4AD34C@comcast.net \
--to=mikestump@comcast.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=hp@axis.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).