From: Jakub Jelinek <jakub@redhat.com>
To: Tamar Christina <Tamar.Christina@arm.com>,
Jeff Law <jeffreyalaw@gmail.com>
Cc: David Edelsohn <dje.gcc@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 5/5] match.pd: Use splits in makefile and make configurable.
Date: Fri, 5 May 2023 22:46:33 +0200 [thread overview]
Message-ID: <ZFVrKVdaLY8hQ9TS@tucnak> (raw)
In-Reply-To: <VI1PR08MB53258204EBD6A2E1D5ABECCAFF729@VI1PR08MB5325.eurprd08.prod.outlook.com>
On Fri, May 05, 2023 at 03:37:47PM +0000, Tamar Christina wrote:
> > 2023-05-05 Jakub Jelinek <jakub@redhat.com>
> >
> > * Makefile.in (check_p_numbers): Rename to one_to_9999, move
> > earlier with helper variables also renamed.
> > (MATCH_SPLUT_SEQ): Use $(wordlist 1,$(NUM_MATCH_SPLITS),$(one_to_9999))
> > instead of $(shell seq 1 $(NUM_MATCH_SPLITS)).
> > (check_p_subdirs): Use $(one_to_9999) instead of $(check_p_numbers).
Passed bootstrap/regtest on x86_64-linux and i686-linux, ok for trunk?
Jakub
next prev parent reply other threads:[~2023-05-05 20:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 14:59 David Edelsohn
2023-05-05 15:04 ` Jeff Law
2023-05-05 15:08 ` Tamar Christina
2023-05-05 15:13 ` Jeff Law
2023-05-05 15:17 ` Jakub Jelinek
2023-05-05 15:22 ` Tamar Christina
2023-05-05 15:33 ` Jakub Jelinek
2023-05-05 15:37 ` Tamar Christina
2023-05-05 15:41 ` David Edelsohn
2023-05-05 20:46 ` Jakub Jelinek [this message]
2023-05-05 23:32 ` Jeff Law
-- strict thread matches above, loose matches on Subject: below --
2023-04-28 10:44 Tamar Christina
2023-04-30 19:46 ` Jeff Law
2023-05-02 7:08 ` Tamar Christina
2023-05-03 15:18 ` Kyrylo Tkachov
2023-05-04 9:56 ` Tamar Christina
2023-05-04 23:25 ` Jeff Law
2023-05-05 12:51 ` Tamar Christina
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=ZFVrKVdaLY8hQ9TS@tucnak \
--to=jakub@redhat.com \
--cc=Tamar.Christina@arm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.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).