LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: tip-bot for Sandipan Das <tipbot@zytor.com> To: linux-tip-commits@vger.kernel.org Cc: hpa@zytor.com, sandipan@linux.vnet.ibm.com, linux-kernel@vger.kernel.org, tglx@linutronix.de, jolsa@redhat.com, naveen.n.rao@linux.vnet.ibm.com, acme@redhat.com, mingo@kernel.org Subject: [tip:perf/urgent] perf tests clang: Fix function name for clang IR test Date: Mon, 9 Apr 2018 22:31:20 -0700 [thread overview] Message-ID: <tip-fcbd8fa44664e99a5d8c7ab97f1afdd82472f973@git.kernel.org> (raw) In-Reply-To: <20180404180419.19056-3-sandipan@linux.vnet.ibm.com> Commit-ID: fcbd8fa44664e99a5d8c7ab97f1afdd82472f973 Gitweb: https://git.kernel.org/tip/fcbd8fa44664e99a5d8c7ab97f1afdd82472f973 Author: Sandipan Das <sandipan@linux.vnet.ibm.com> AuthorDate: Wed, 4 Apr 2018 23:34:19 +0530 Committer: Arnaldo Carvalho de Melo <acme@redhat.com> CommitDate: Mon, 9 Apr 2018 11:13:09 -0300 perf tests clang: Fix function name for clang IR test As stated in tests/llvm-src-base.c, the name of the bpf function should be "bpf_func__SyS_epoll_pwait" but this clang test fails as it tries to lookup "bpf_func__SyS_epoll_wait". Before applying patch: 55: builtin clang support : 55.1: builtin clang compile C source to IR : FAILED! 55.2: builtin clang compile C source to ELF object : Skip After applying patch: 55: builtin clang support : 55.1: builtin clang compile C source to IR : Ok 55.2: builtin clang compile C source to ELF object : Ok Signed-off-by: Sandipan Das <sandipan@linux.vnet.ibm.com> Tested-by: Arnaldo Carvalho de Melo <acme@redhat.com> Cc: Jiri Olsa <jolsa@redhat.com> Cc: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com> Fixes: e67d52d411c3 ("perf clang: Update test case to use real BPF script") Link: http://lkml.kernel.org/r/20180404180419.19056-3-sandipan@linux.vnet.ibm.com Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com> --- tools/perf/util/c++/clang-test.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/perf/util/c++/clang-test.cpp b/tools/perf/util/c++/clang-test.cpp index a4014d786676..7b042a5ebc68 100644 --- a/tools/perf/util/c++/clang-test.cpp +++ b/tools/perf/util/c++/clang-test.cpp @@ -41,7 +41,7 @@ int test__clang_to_IR(void) if (!M) return -1; for (llvm::Function& F : *M) - if (F.getName() == "bpf_func__SyS_epoll_wait") + if (F.getName() == "bpf_func__SyS_epoll_pwait") return 0; return -1; }
next prev parent reply other threads:[~2018-04-10 5:31 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-04-04 18:04 [PATCH 1/3] perf tools: Fix perf builds with clang support Sandipan Das 2018-04-04 18:04 ` [PATCH 2/3] perf clang: Add support for recent clang versions Sandipan Das 2018-04-10 5:30 ` [tip:perf/urgent] " tip-bot for Sandipan Das 2018-04-04 18:04 ` [PATCH 3/3] perf tests clang: Fix function name for clang IR test Sandipan Das 2018-04-10 5:31 ` tip-bot for Sandipan Das [this message] 2018-04-10 5:30 ` [tip:perf/urgent] perf tools: Fix perf builds with clang support tip-bot for Sandipan Das
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-fcbd8fa44664e99a5d8c7ab97f1afdd82472f973@git.kernel.org \ --to=tipbot@zytor.com \ --cc=acme@redhat.com \ --cc=hpa@zytor.com \ --cc=jolsa@redhat.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-tip-commits@vger.kernel.org \ --cc=mingo@kernel.org \ --cc=naveen.n.rao@linux.vnet.ibm.com \ --cc=sandipan@linux.vnet.ibm.com \ --cc=tglx@linutronix.de \ /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: linkBe 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 NNTP newsgroup(s).