From: Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>
To: Tamar Christina <Tamar.Christina@arm.com>,
Jeff Law <jeffreyalaw@gmail.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: nd <nd@arm.com>, "bonzini@gnu.org" <bonzini@gnu.org>,
"neroden@gcc.gnu.org" <neroden@gcc.gnu.org>,
"aoliva@gcc.gnu.org" <aoliva@gcc.gnu.org>,
"Ralf.Wildenhues@gmx.de" <Ralf.Wildenhues@gmx.de>
Subject: RE: [PATCH 5/5] match.pd: Use splits in makefile and make configurable.
Date: Wed, 3 May 2023 15:18:43 +0000 [thread overview]
Message-ID: <PAXPR08MB6926F9D6D324EA3B74DECEF6936C9@PAXPR08MB6926.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <VI1PR08MB5325F5465DDD6F3AEB5E310BFF6F9@VI1PR08MB5325.eurprd08.prod.outlook.com>
> -----Original Message-----
> From: Gcc-patches <gcc-patches-
> bounces+kyrylo.tkachov=arm.com@gcc.gnu.org> On Behalf Of Tamar
> Christina via Gcc-patches
> Sent: Tuesday, May 2, 2023 8:08 AM
> To: Jeff Law <jeffreyalaw@gmail.com>; gcc-patches@gcc.gnu.org
> Cc: nd <nd@arm.com>; bonzini@gnu.org; neroden@gcc.gnu.org;
> aoliva@gcc.gnu.org; Ralf.Wildenhues@gmx.de
> Subject: RE: [PATCH 5/5] match.pd: Use splits in makefile and make
> configurable.
>
> > -----Original Message-----
> > From: Jeff Law <jeffreyalaw@gmail.com>
> > Sent: Sunday, April 30, 2023 8:46 PM
> > To: Tamar Christina <Tamar.Christina@arm.com>; gcc-patches@gcc.gnu.org
> > Cc: nd <nd@arm.com>; bonzini@gnu.org; neroden@gcc.gnu.org;
> > aoliva@gcc.gnu.org; Ralf.Wildenhues@gmx.de
> > Subject: Re: [PATCH 5/5] match.pd: Use splits in makefile and make
> > configurable.
> >
> >
> >
> > On 4/28/23 04:44, Tamar Christina via Gcc-patches wrote:
> > > Hi All,
> > >
> > > This updates the build system to split up match.pd files into chunks of 10.
> > > This also introduces a new flag --with-matchpd-partitions which can be
> > > used to change the number of partitions.
> > >
> > > For the analysis of why 10 please look at the previous patch in the series.
> > >
> > > Bootstrapped Regtested on aarch64-none-linux-gnu and no issues.
> > >
> > > Ok for master?
> > >
> > > Thanks,
> > > Tamar
> > >
> > > gcc/ChangeLog:
> > >
> > > PR bootstrap/84402
> > > * Makefile.in (NUM_MATCH_SPLITS, MATCH_SPLITS_SEQ,
> > > GIMPLE_MATCH_PD_SEQ_SRC, GIMPLE_MATCH_PD_SEQ_O,
> > > GENERIC_MATCH_PD_SEQ_SRC, GENERIC_MATCH_PD_SEQ_O): New.
> > > (OBJS, MOSTLYCLEANFILES, .PRECIOUS): Use them.
> > > (s-match): Split into s-generic-match and s-gimple-match.
> > > * configure.ac (with-matchpd-partitions,
> > > DEFAULT_MATCHPD_PARTITIONS): New.
> > > * configure: Regenerate.
> > This looks pretty reasonable to me. Are there any patches left in this series
> > that need review? I'm very much looking forward to build time provements
> > related to this patch, particularly for targets that I bootstrap with qemu
> > emulation -- we take multiple hours to build gimple-match and the ability to
> > parallelize those component builds should be a significant win.
>
> Hi,
>
> No this is the last one, Richi already approved the rest but he didn't feel he
> had
> enough knowledge about the build system to say if this code was portable
> enough.
I'm looking forward to this going as well for improved bootstrap times, thanks for working on this!
>
> So just waiting on this one and can commit the series.
Can we treat Jeff's LGTM above as an ok given his global reviewer position?
Thanks,
Kyrill
>
> Cheers,
> Tamar
> >
> > jeff
next prev parent reply other threads:[~2023-05-03 15:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2023-05-04 9:56 ` Tamar Christina
2023-05-04 23:25 ` Jeff Law
2023-05-05 12:51 ` Tamar Christina
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
2023-05-05 23:32 ` Jeff Law
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=PAXPR08MB6926F9D6D324EA3B74DECEF6936C9@PAXPR08MB6926.eurprd08.prod.outlook.com \
--to=kyrylo.tkachov@arm.com \
--cc=Ralf.Wildenhues@gmx.de \
--cc=Tamar.Christina@arm.com \
--cc=aoliva@gcc.gnu.org \
--cc=bonzini@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=nd@arm.com \
--cc=neroden@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: 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).