From: tip-bot for Masahiro Yamada <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: hpa@zytor.com, mingo@kernel.org, yamada.masahiro@socionext.com,
jolsa@kernel.org, adrian.hunter@intel.com, acme@redhat.com,
linux-kernel@vger.kernel.org, lukas@wunner.de,
aaro.koskinen@nokia.com, tglx@linutronix.de
Subject: [tip:perf/core] tools build: Use .s extension for preprocessed assembler code
Date: Sat, 5 Mar 2016 00:18:16 -0800 [thread overview]
Message-ID: <tip-676787939ef8ccfcf8039104f766ebe5ebe23924@git.kernel.org> (raw)
In-Reply-To: <1454263140-19670-1-git-send-email-yamada.masahiro@socionext.com>
Commit-ID: 676787939ef8ccfcf8039104f766ebe5ebe23924
Gitweb: http://git.kernel.org/tip/676787939ef8ccfcf8039104f766ebe5ebe23924
Author: Masahiro Yamada <yamada.masahiro@socionext.com>
AuthorDate: Mon, 1 Feb 2016 02:59:00 +0900
Committer: Arnaldo Carvalho de Melo <acme@redhat.com>
CommitDate: Thu, 3 Mar 2016 11:10:37 -0300
tools build: Use .s extension for preprocessed assembler code
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>
Acked-by: Jiri Olsa <jolsa@kernel.org>
Cc: Aaro Koskinen <aaro.koskinen@nokia.com>
Cc: Adrian Hunter <adrian.hunter@intel.com>
Cc: Lukas Wunner <lukas@wunner.de>
Link: http://lkml.kernel.org/r/1454263140-19670-1-git-send-email-yamada.masahiro@socionext.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.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)
prev parent reply other threads:[~2016-03-05 8:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-31 17:59 [PATCH] tools build: use " Masahiro Yamada
2016-03-01 5:31 ` Masahiro Yamada
2016-03-01 13:20 ` Arnaldo Carvalho de Melo
2016-03-01 13:06 ` Jiri Olsa
2016-03-05 8:18 ` tip-bot for Masahiro Yamada [this message]
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=tip-676787939ef8ccfcf8039104f766ebe5ebe23924@git.kernel.org \
--to=tipbot@zytor.com \
--cc=aaro.koskinen@nokia.com \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=hpa@zytor.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome