All of lore.kernel.org
 help / color / mirror / Atom feed
From: twd2 <twd2.me@gmail.com>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: palmer@dabbelt.com, paul.walmsley@sifive.com,
	aou@eecs.berkeley.edu, linux-riscv@lists.infradead.org,
	clang-built-linux@googlegroups.com,
	Nathan Chancellor <nathan@kernel.org>,
	arnd@arndb.de
Subject: Re: [PATCH 3/3] RISC-V: build: Allow LTO to be selected
Date: Wed, 21 Jul 2021 05:18:56 +0800	[thread overview]
Message-ID: <970c36ea-c5a6-2b47-3024-7cbbf428ebfa@gmail.com> (raw)
In-Reply-To: <475c3797-e048-97bb-095a-c55aff38bc42@gmail.com>

Also, I tried `defconfig` with Full/Thin LTO.  It can boot and the
busybox shell works.

I'll put this information into the next version of the patch series.


Thanks.
Wende


On 2021/7/21 2:29, twd2 wrote:
> Hi, I just tried to compile with this patch and `allyesconfig` except
> COMPILE_TEST, FTRACE, KASAN, GCOV, and XFS [1].  It finishes with no
> issue, and takes ~22 min and ~25 GiB.  BTW, the kernel panics during boot
> even built with GCC, so I didn't do further tests :( .
>
> Command used: ARCH=riscv LLVM=1 LLVM_IAS=1 make HOSTCC=gcc vmlinux -j16
> Kernel version: commit 2734d6c1b1a0 ("Linux 5.14-rc2")
> LLVM version: commit 1b61d837b9d0 ("[Inline] Add test for PR50589 (NFC)")
> The `.config` file is attached.
>
> [1] https://github.com/ClangBuiltLinux/linux/issues/1215
>
> On 2021/7/20 5:25, Nick Desaulniers wrote:
>> On Mon, Jul 19, 2021 at 1:53 PM Wende Tan <twd2.me@gmail.com> wrote:
>>
>> Consider adding a little more detail to the commit message.
>>
>> In our experience with other architectures, we've hit numerous
>> compiler and kernel issues especially with allyesconfigs. Has that
>> been your experience with riscv?  It would be good to know if you've
>> hit issues with LTO plus certain configs, so that we have confirmation
>> others have seen these issues and so that we can triage fixes.
>>
>>> Signed-off-by: Wende Tan <twd2.me@gmail.com>
>>> ---
>>>  arch/riscv/Kconfig | 2 ++
>>>  1 file changed, 2 insertions(+)
>>>
>>> diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig
>>> index 8fcceb8eda07..b593e5031c79 100644
>>> --- a/arch/riscv/Kconfig
>>> +++ b/arch/riscv/Kconfig
>>> @@ -34,6 +34,8 @@ config RISCV
>>>         select ARCH_OPTIONAL_KERNEL_RWX if ARCH_HAS_STRICT_KERNEL_RWX
>>>         select ARCH_OPTIONAL_KERNEL_RWX_DEFAULT
>>>         select ARCH_SUPPORTS_HUGETLBFS if MMU
>>> +       select ARCH_SUPPORTS_LTO_CLANG
>>> +       select ARCH_SUPPORTS_LTO_CLANG_THIN
>>>         select ARCH_USE_MEMTEST
>>>         select ARCH_WANT_DEFAULT_TOPDOWN_MMAP_LAYOUT if MMU
>>>         select ARCH_WANT_FRAME_POINTERS
>>> --


_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

      reply	other threads:[~2021-07-20 21:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-19 20:53 [PATCH 3/3] RISC-V: build: Allow LTO to be selected Wende Tan
2021-07-19 21:25 ` Nick Desaulniers
2021-07-20 18:29   ` twd2
2021-07-20 21:18     ` twd2 [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=970c36ea-c5a6-2b47-3024-7cbbf428ebfa@gmail.com \
    --to=twd2.me@gmail.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=arnd@arndb.de \
    --cc=clang-built-linux@googlegroups.com \
    --cc=linux-riscv@lists.infradead.org \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --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 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.