From: Wang YanQing <udknight@gmail.com>
To: Brian Gerst <brgerst@gmail.com>, mmarek@suse.com
Cc: linux-kbuild@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
yamada.masahiro@socionext.com
Subject: Re: [PATCH] kbuild: support make dir/file.i for *.S
Date: Tue, 15 Dec 2015 00:14:01 +0800 [thread overview]
Message-ID: <20151214161401.GA8036@udknight> (raw)
In-Reply-To: <CAMzpN2jG+mKQdAxKnvTebQtF1J79pC+E4QxELLO_C2K6ZR8PzA@mail.gmail.com>
On Sat, Dec 12, 2015 at 02:13:03PM -0500, Brian Gerst wrote:
> On Thu, Dec 10, 2015 at 11:33 AM, Wang YanQing <udknight@gmail.com> wrote:
> > This feature could reduce a little time to expand all
> > the macros in *.S for reading.
> >
> > Signed-off-by: Wang YanQing <udknight@gmail.com>
> > ---
> > Makefile | 2 ++
> > scripts/Makefile.build | 6 ++++++
> > 2 files changed, 8 insertions(+)
> >
> > diff --git a/Makefile b/Makefile
> > index 7558c9c..d7e2060 100644
> > --- a/Makefile
> > +++ b/Makefile
> > @@ -1552,6 +1552,8 @@ endif
> > $(Q)$(MAKE) $(build)=$(build-dir) $(target-dir)$(notdir $@)
> > %.s: %.S prepare scripts FORCE
> > $(Q)$(MAKE) $(build)=$(build-dir) $(target-dir)$(notdir $@)
> > +%.i: %.S prepare scripts FORCE
> > + $(Q)$(MAKE) $(build)=$(build-dir) $(target-dir)$(notdir $@)
> > %.o: %.S prepare scripts FORCE
> > $(Q)$(MAKE) $(build)=$(build-dir) $(target-dir)$(notdir $@)
> > %.symtypes: %.c prepare scripts FORCE
> > diff --git a/scripts/Makefile.build b/scripts/Makefile.build
> > index 2c47f9c..2a51d49 100644
> > --- a/scripts/Makefile.build
> > +++ b/scripts/Makefile.build
> > @@ -287,6 +287,12 @@ cmd_as_s_S = $(CPP) $(a_flags) -o $@ $<
> > $(obj)/%.s: $(src)/%.S FORCE
> > $(call if_changed_dep,as_s_S)
> >
> > +quiet_cmd_cc_i_S = CPP $(quiet_modtag) $@
> > +cmd_cc_i_S = $(CPP) $(a_flags) -o $@ $<
> > +
> > +$(obj)/%.i: $(src)/%.S FORCE
> > + $(call if_changed_dep,cc_i_S)
> > +
> > quiet_cmd_as_o_S = AS $(quiet_modtag) $@
> > cmd_as_o_S = $(CC) $(a_flags) -c -o $@ $<
>
> *.s (lower case) is the suffix used for preprocessed assembly files,
> and there is already a rule for that. *.i is for preprocessed C
> files.
Agreed, you are right!
Thanks.
next prev parent reply other threads:[~2015-12-14 17:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 16:33 [PATCH] kbuild: support make dir/file.i for *.S Wang YanQing
2015-12-11 16:29 ` Michal Marek
2015-12-12 19:13 ` Brian Gerst
2015-12-13 8:17 ` Masahiro Yamada
2015-12-14 16:14 ` Wang YanQing [this message]
2015-12-14 17:16 ` Michal Marek
2015-12-15 1:41 ` Masahiro Yamada
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=20151214161401.GA8036@udknight \
--to=udknight@gmail.com \
--cc=brgerst@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=yamada.masahiro@socionext.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