All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64/signal: Clean up SVE/SME feature checking inconsistency
Date: Fri, 24 Jun 2022 15:10:46 +0100	[thread overview]
Message-ID: <20220624141046.GA19170@willie-the-truck> (raw)
In-Reply-To: <YrW75yu/Qn5EmXNO@sirena.org.uk>

On Fri, Jun 24, 2022 at 02:28:07PM +0100, Mark Brown wrote:
> On Thu, Jun 23, 2022 at 06:47:38PM +0100, Will Deacon wrote:
> 
> > This breaks the allnoconfig build for me:
> 
> > ld.lld: error: undefined symbol: restore_sve_fpsimd_context
> > >>> referenced by signal.c
> > >>>               kernel/signal.o:(__arm64_sys_rt_sigreturn) in archive arch/arm64/built-in.a
> > make: *** [Makefile:1164: vmlinux] Error 1
> 
> I can't reproduce that here - could you confirm exactly what tree you
> applied against and what toolchain you're using?  I'm normally using
> clang 15 at the minute, 14 seems fine too, and applied against both
> -next and v5.19-rc3 all of which are building an allnoconfig happily for
> me.

I can reproduce the issue with just this patch applied on top of -rc3.
I'll give your v2 a try, bu FWIW I'm using clang 12.0.6 and building
using:

$ make LLVM=1 ARCH=arm64 mrproper allnoconfig
$ make LLVM=1 ARCH=arm64 -j100

Will

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

  reply	other threads:[~2022-06-24 14:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13 21:01 [PATCH] arm64/signal: Clean up SVE/SME feature checking inconsistency Mark Brown
2022-06-23 17:47 ` Will Deacon
2022-06-24 13:28   ` Mark Brown
2022-06-24 14:10     ` Will Deacon [this message]
2022-06-24 14:19       ` Mark Brown

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=20220624141046.GA19170@willie-the-truck \
    --to=will@kernel.org \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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.