From: Conor Dooley <conor@kernel.org>
To: Jisheng Zhang <jszhang@kernel.org>
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: vdso: fix build with llvm
Date: Mon, 31 Oct 2022 19:21:20 +0000 [thread overview]
Message-ID: <Y2AgMLzH/RF1gQkB@spud> (raw)
In-Reply-To: <20221031182943.2453-1-jszhang@kernel.org>
On Tue, Nov 01, 2022 at 02:29:43AM +0800, Jisheng Zhang wrote:
> Even after commit 89fd4a1df829 ("riscv: jump_label: mark arguments as
> const to satisfy asm constraints"), building with CC_OPTIMIZE_FOR_SIZE
> + LLVM=1 can reproduce below build error:
>
> CC arch/riscv/kernel/vdso/vgettimeofday.o
> In file included from <built-in>:4:
> In file included from lib/vdso/gettimeofday.c:5:
> In file included from include/vdso/datapage.h:17:
> In file included from
> include/vdso/processor.h:10:
> In file included from
> arch/riscv/include/asm/vdso/processor.h:7:
> In file included from
> include/linux/jump_label.h:112:
> arch/riscv/include/asm/jump_label.h:42:3: error:
> invalid operand fo
> r inline asm constraint 'i'
> " .option push \n\t"
> ^
> 1 error generated.
Tested-by: Conor Dooley <conor.dooley@microchip.com>
>
> I think the problem is when "-Os" is passed as CFLAGS, it's removed by
> "CFLAGS_REMOVE_vgettimeofday.o = $(CC_FLAGS_FTRACE) -Os" which is
> introduced in commit e05d57dcb8c7 ("riscv: Fixup __vdso_gettimeofday
> broke dynamic ftrace"), thus no optimization at all for vgettimeofday.c
> arm64 does remove "-Os" as well, but it forces "-O2" after removing
> "-Os".
>
> I compared the generated vgettimeofday.o with "-O2" and "-Os",
> I think no big performance difference. So let's tell the kbuild not
> to remove "-Os" rather than follow arm64 style.
>
> vdso related performance can be improved a lot when building kernel with
> CC_OPTIMIZE_FOR_SIZE after this commit, ("-Os" VS no optimization)
>
> Fixes: e05d57dcb8c7 ("riscv: Fixup __vdso_gettimeofday broke dynamic ftrace")
> Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
> ---
> arch/riscv/kernel/vdso/Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/riscv/kernel/vdso/Makefile b/arch/riscv/kernel/vdso/Makefile
> index f2e065671e4d..84ac0fe612e7 100644
> --- a/arch/riscv/kernel/vdso/Makefile
> +++ b/arch/riscv/kernel/vdso/Makefile
> @@ -30,7 +30,7 @@ obj-y += vdso.o
> CPPFLAGS_vdso.lds += -P -C -U$(ARCH)
>
> # Disable -pg to prevent insert call site
> -CFLAGS_REMOVE_vgettimeofday.o = $(CC_FLAGS_FTRACE) -Os
> +CFLAGS_REMOVE_vgettimeofday.o = $(CC_FLAGS_FTRACE)
>
> # Disable profiling and instrumentation for VDSO code
> GCOV_PROFILE := n
> --
> 2.37.2
>
next prev parent reply other threads:[~2022-10-31 19:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 18:29 [PATCH] riscv: vdso: fix build with llvm Jisheng Zhang
2022-10-31 19:21 ` Conor Dooley [this message]
2022-11-01 14:59 ` kernel test robot
2022-11-01 15:24 ` Conor Dooley
2022-11-02 17:07 ` Jisheng Zhang
2022-11-10 22:45 ` Palmer Dabbelt
2022-11-10 22:50 ` patchwork-bot+linux-riscv
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=Y2AgMLzH/RF1gQkB@spud \
--to=conor@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=jszhang@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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 NNTP newsgroup(s).