linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Samuel Holland <samuel.holland@sifive.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	Christoph Hellwig <hch@lst.de>, kernel test robot <lkp@intel.com>
Subject: Re: [akpm-mm:mm-nonmm-unstable 53/62] lib/raid6/recov_neon_inner.c:7:10: fatal error: 'arm_neon.h' file not found
Date: Fri, 29 Mar 2024 10:25:36 -0500	[thread overview]
Message-ID: <3a2329e3-4006-4484-8e36-af11d8830b3f@sifive.com> (raw)
In-Reply-To: <20240329152053.GA2647510@dev-arch.thelio-3990X>

On 2024-03-29 10:20 AM, Nathan Chancellor wrote:
> On Fri, Mar 29, 2024 at 12:27:57PM +0800, kernel test robot wrote:
>> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-nonmm-unstable
>> head:   b065e14a3960a495216a032e6d383c104147c9ef
>> commit: aa73a95380b4ef76ccf00344b777d0d415026b7b [53/62] lib/raid6: use CC_FLAGS_FPU for NEON CFLAGS
>> config: arm-randconfig-002-20240329 (https://download.01.org/0day-ci/archive/20240329/202403291210.ioK7bfPA-lkp@intel.com/config)
>> compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project 79ba323bdd0843275019e16b6e9b35133677c514)
>> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240329/202403291210.ioK7bfPA-lkp@intel.com/reproduce)
>>
>> If you fix the issue in a separate patch/commit (i.e. not just a new version of
>> the same patch/commit), kindly add following tags
>> | Reported-by: kernel test robot <lkp@intel.com>
>> | Closes: https://lore.kernel.org/oe-kbuild-all/202403291210.ioK7bfPA-lkp@intel.com/
>>
>> All errors (new ones prefixed by >>):
>>
>>>> lib/raid6/recov_neon_inner.c:7:10: fatal error: 'arm_neon.h' file not found
>>        7 | #include <arm_neon.h>
>>          |          ^~~~~~~~~~~~
>>    1 error generated.
> 
> Looks like the CFLAGS for recov_neon_inner.o got lost. This resolves it
> for me.

Right. I fixed this in v4:

https://lore.kernel.org/linux-kernel/20240329072441.591471-7-samuel.holland@sifive.com/

Regards,
Samuel

> diff --git a/lib/raid6/Makefile b/lib/raid6/Makefile
> index c71984e04c4d..0e88bfe6445b 100644
> --- a/lib/raid6/Makefile
> +++ b/lib/raid6/Makefile
> @@ -60,10 +60,12 @@ CFLAGS_neon1.o += $(CC_FLAGS_FPU)
>  CFLAGS_neon2.o += $(CC_FLAGS_FPU)
>  CFLAGS_neon4.o += $(CC_FLAGS_FPU)
>  CFLAGS_neon8.o += $(CC_FLAGS_FPU)
> +CFLAGS_recov_neon_inner.o += $(CC_FLAGS_FPU)
>  CFLAGS_REMOVE_neon1.o += $(CC_FLAGS_NO_FPU)
>  CFLAGS_REMOVE_neon2.o += $(CC_FLAGS_NO_FPU)
>  CFLAGS_REMOVE_neon4.o += $(CC_FLAGS_NO_FPU)
>  CFLAGS_REMOVE_neon8.o += $(CC_FLAGS_NO_FPU)
> +CFLAGS_REMOVE_recov_neon_inner.o += $(CC_FLAGS_NO_FPU)
>  targets += neon1.c neon2.c neon4.c neon8.c
>  $(obj)/neon%.c: $(src)/neon.uc $(src)/unroll.awk FORCE
>  	$(call if_changed,unroll)



      reply	other threads:[~2024-03-29 15:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-29  4:27 kernel test robot
2024-03-29 15:20 ` Nathan Chancellor
2024-03-29 15:25   ` Samuel Holland [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=3a2329e3-4006-4484-8e36-af11d8830b3f@sifive.com \
    --to=samuel.holland@sifive.com \
    --cc=akpm@linux-foundation.org \
    --cc=hch@lst.de \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=nathan@kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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