public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jojo R <jiejie_rong@c-sky.com>
To: Richard Sandiford <richard.sandiford@arm.com>
Cc: segher@kernel.crashing.org, yunhai.syh@alibaba-inc.com,
	 gcc-patches@gcc.gnu.org, joseph@codesourcery.com
Subject: Re: [PATCH v7] genemit.c (main): split insn-emit.c for compiling parallelly
Date: Wed, 4 Nov 2020 10:25:11 +0800	[thread overview]
Message-ID: <8bff8454-9577-4527-8f93-4fbb502404cf@Spark> (raw)
In-Reply-To: <mpt4kmbybob.fsf@arm.com>


Jojo
在 2020年10月30日 +0800 PM11:29,Richard Sandiford <richard.sandiford@arm.com>,写道:
> Jojo R <jiejie_rong@c-sky.com> writes:
> > Jojo
> > 在 2020年10月27日 +0800 PM10:14,Richard Sandiford <richard.sandiford@arm.com>,写道:
> > > Jojo R <jiejie_rong@c-sky.com> writes:
> > > > gcc/ChangeLog:
> > > >
> > > > * genemit.c (main): Print 'split line'.
> > > > * Makefile.in (insn-emit.c): Define split count and file
> > > >
> > > > ---
> > > > gcc/Makefile.in | 19 +++++++++
> > > > gcc/genemit.c | 104 +++++++++++++++++++++++++++++-------------------
> > > > 2 files changed, 83 insertions(+), 40 deletions(-)
> > > >
> > > > diff --git a/gcc/Makefile.in b/gcc/Makefile.in
> > > > index 79e854aa938..a7fcc7d5949 100644
> > > > --- a/gcc/Makefile.in
> > > > +++ b/gcc/Makefile.in
> > > > @@ -1258,6 +1258,21 @@ ANALYZER_OBJS = \
> > > > # We put the *-match.o and insn-*.o files first so that a parallel make
> > > > # will build them sooner, because they are large and otherwise tend to be
> > > > # the last objects to finish building.
> > > > +
> > > > +# target overrides
> > > > +-include $(tmake_file)
> > > > +
> > > > +INSN-GENERATED-SPLIT-NUM ?= 0
> > > > +
> > > > +insn-generated-split-num = $(shell i=1; j=`expr $(INSN-GENERATED-SPLIT-NUM) + 1`; \
> > > > + while test $$i -le $$j; do \
> > > > + echo $$i; i=`expr $$i + 1`; \
> > > > + done)
> > > > +
> > > > +insn-emit-split-c := $(foreach o, $(shell for i in $(insn-generated-split-num); do echo $$i; done), insn-emit$(o).c)
> > > > +insn-emit-split-obj = $(patsubst %.c,%.o, $(insn-emit-split-c))
> > > > +$(insn-emit-split-c): insn-emit.c
> > >
> > > Sorry for the slow reply. I stand by what I said in
> > > https://gcc.gnu.org/pipermail/gcc-patches/2020-August/552863.html:
> > >
> > > I think we should use the same wordlist technique as check_p_numbers[0-6].
> > > So I guess the first step would be to rename check_p_numbers[0-6] to
> > > something more general and use it both here and in check_p_numbers.
> > >
> > > I think that would be better than having two different ways of
> > > generating lists of numbers, one directly in make and one calling
> > > out to the shell. But I didn't want to reassert that comment in
> > > case anyone was prepared to approve the patch in its current form.
> > >
> >
> > Ok & Thanks.
> >
> > It’s fixed in patch v8.
>
> Thanks. Like I say, I think we should rename check_p_numbers* at the
> same time, since it's now used for more than just parallel check. Maybe
> s/check_p_numbers/number_series/.

Ok & It’s fixed in patch v9.
>
> But otherwise it looks good.
>
> > > BTW, do you have a copyright assignment on file?
> >
> > I email the patch without copyright, and I think it is same with other gcc community patch.
>
> Some changes can be so small and mechanical that they're not in practice
> copyrightable, but all other changes need a copyright assignment.
> Unfortunately this patch is too complex to fall into the first category.
> See:
>
> https://gcc.gnu.org/contribute.html#legal
>
> for more details about the requirement and process.
>

From the patch of https://gcc.gnu.org/legacy-ml/gcc-patches/2018-07/msg01289.html
we have supported c-sky port in GCC backend, I think we also need to submit
a copyright for it and have submitted that.
I am contacting assign@gnu.org to check it.

Thanks.
> Thanks,
> Richard

  reply	other threads:[~2020-11-04  2:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <jiejie_rong@c-sky.com@genemit.c_(main):_split_insn-emit.c_for_compiling_parallelly>
2020-09-15  9:15 ` Jojo R
2020-09-27  2:34   ` Jojo R
2020-10-08  2:01     ` Jojo R
2020-10-24  6:02       ` Jojo R
2020-10-27  5:59         ` Jojo R
2020-10-27 14:14   ` Richard Sandiford
2020-10-30  9:41     ` Jojo R
2020-10-30 15:29       ` Richard Sandiford
2020-11-04  2:25         ` Jojo R [this message]
2020-10-30  9:42 ` [PATCH v8] " Jojo R
2020-11-04  1:53 ` [PATCH v9] " Jojo R
2020-11-04 11:06   ` Richard Sandiford
2020-11-06 10:12   ` Richard Sandiford

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=8bff8454-9577-4527-8f93-4fbb502404cf@Spark \
    --to=jiejie_rong@c-sky.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=joseph@codesourcery.com \
    --cc=richard.sandiford@arm.com \
    --cc=segher@kernel.crashing.org \
    --cc=yunhai.syh@alibaba-inc.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).