From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Aaro Koskinen <aaro.koskinen@nokia.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Lukas Wunner <lukas@wunner.de>, Jiri Olsa <jolsa@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tools build: use .s extension for preprocessed assembler code
Date: Tue, 1 Mar 2016 10:20:47 -0300 [thread overview]
Message-ID: <20160301132047.GA2524@redhat.com> (raw)
In-Reply-To: <CAK7LNAT0YCHbh7CfWKG1bZiJCXNXk7Jv6sdQz_9Sa6OG5zScrg@mail.gmail.com>
Em Tue, Mar 01, 2016 at 02:31:10PM +0900, Masahiro Yamada escreveu:
> Hi Arnaldo,
>
> Do you have any comment on this patch?
Sorry for the delay, I saw this patch, found no problems with it but was
waiting for Jiri's Ack, which he provided today, applying, thanks.
- Arnaldo
> (I hope I am addressing myself to a right person.
> "git log --pretty=fuller tools/build/Makefile.build" showed that
> several patches in this area had been applied by you.)
>
>
> Thanks,
>
>
> 2016-02-01 2:59 GMT+09:00 Masahiro Yamada <yamada.masahiro@socionext.com>:
> > The "man gcc" says .i extension represents the file is C source code
> > that should not be preprocessed. Here, .s should be used.
> >
> > For clarification,
> > .c ---(preprocess)---> .i
> > .S ---(preprocess)---> .s
> >
> > Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> > ---
> >
> > tools/build/Makefile.build | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/tools/build/Makefile.build b/tools/build/Makefile.build
> > index 4a96473..ee566e8 100644
> > --- a/tools/build/Makefile.build
> > +++ b/tools/build/Makefile.build
> > @@ -85,7 +85,7 @@ $(OUTPUT)%.i: %.c FORCE
> > $(call rule_mkdir)
> > $(call if_changed_dep,cc_i_c)
> >
> > -$(OUTPUT)%.i: %.S FORCE
> > +$(OUTPUT)%.s: %.S FORCE
> > $(call rule_mkdir)
> > $(call if_changed_dep,cc_i_c)
> >
> > --
> > 1.9.1
> >
>
>
>
> --
> Best Regards
> Masahiro Yamada
next prev parent reply other threads:[~2016-03-01 13:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-31 17:59 [PATCH] tools build: use .s extension for preprocessed assembler code Masahiro Yamada
2016-03-01 5:31 ` Masahiro Yamada
2016-03-01 13:20 ` Arnaldo Carvalho de Melo [this message]
2016-03-01 13:06 ` Jiri Olsa
2016-03-05 8:18 ` [tip:perf/core] tools build: Use " tip-bot for 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=20160301132047.GA2524@redhat.com \
--to=acme@redhat.com \
--cc=aaro.koskinen@nokia.com \
--cc=adrian.hunter@intel.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas@wunner.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.