mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Clark <james.clark@arm.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>,
	open list <linux-kernel@vger.kernel.org>,
	coresight@lists.linaro.org,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Cc: Mathieu Poirier <mathieu.poirier@linaro.org>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Mike Leach <mike.leach@linaro.org>, Leo Yan <leo.yan@linaro.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Arnd Bergmann <arnd@arndb.de>, Mark Brown <broonie@kernel.org>
Subject: Re: coresight-etm4x-core.c:969:26: error: 'ID_AA64DFR0_TRACEVER_SHIFT' undeclared
Date: Tue, 20 Sep 2022 14:50:08 +0100	[thread overview]
Message-ID: <7dbf6fc6-5cd5-4493-af55-6ebf6b97a019@arm.com> (raw)
In-Reply-To: <CA+G9fYtpNsjRzQdxFvLjVmG9XX95B6DtaviHq3oG6awGYTqGSw@mail.gmail.com>



On 20/09/2022 12:39, Naresh Kamboju wrote:
> Following build warnings / errors noticed while building arm64 coresight
> on linux next-20220919 and next-20220920.

Fix is here:
https://lists.linaro.org/archives/list/coresight@lists.linaro.org/thread/OS4F43WGOYGQUJHISR2PZQPE3FUQ7DXH/

> 
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> 
> make --silent --keep-going --jobs=8
> O=/home/tuxbuild/.cache/tuxmake/builds/1/build
> CROSS_COMPILE_COMPAT=arm-linux-gnueabihf- ARCH=arm64
> CROSS_COMPILE=aarch64-linux-gnu- 'CC=sccache aarch64-linux-gnu-gcc'
> 'HOSTCC=sccache gcc'
> 
> drivers/hwtracing/coresight/coresight-etm4x-core.c: In function
> 'cpu_supports_sysreg_trace':
> drivers/hwtracing/coresight/coresight-etm4x-core.c:969:26: error:
> 'ID_AA64DFR0_TRACEVER_SHIFT' undeclared (first use in this function);
> did you mean 'ID_AA64DFR0_EL1_TraceVer_SHIFT'?
>   969 |         return ((dfr0 >> ID_AA64DFR0_TRACEVER_SHIFT) & 0xfUL) > 0;
>       |                          ^~~~~~~~~~~~~~~~~~~~~~~~~~
>       |                          ID_AA64DFR0_EL1_TraceVer_SHIFT
> drivers/hwtracing/coresight/coresight-etm4x-core.c:969:26: note: each
> undeclared identifier is reported only once for each function it
> appears in
> drivers/hwtracing/coresight/coresight-etm4x-core.c: In function
> 'cpu_detect_trace_filtering':
> drivers/hwtracing/coresight/coresight-etm4x-core.c:1057:57: error:
> 'ID_AA64DFR0_TRACE_FILT_SHIFT' undeclared (first use in this
> function); did you mean 'ID_AA64PFR0_EL1_DIT_SHIFT'?
>  1057 |         if (!cpuid_feature_extract_unsigned_field(dfr0,
> ID_AA64DFR0_TRACE_FILT_SHIFT))
>       |
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
>       |
> ID_AA64PFR0_EL1_DIT_SHIFT
> drivers/hwtracing/coresight/coresight-etm4x-core.c: In function
> 'cpu_supports_sysreg_trace':
> drivers/hwtracing/coresight/coresight-etm4x-core.c:970:1: error:
> control reaches end of non-void function [-Werror=return-type]
>   970 | }
>       | ^
> cc1: some warnings being treated as errors
> 
> Regressions found on arm64:
>    - build-clang-13-lkftconfig
>    - build-gcc-11-lkftconfig-devicetree
>    - build-gcc-11-lkftconfig-kunit
>    - build-gcc-11-lkftconfig-perf
>    - build-gcc-11-lkftconfig-64k_page_size
>    - build-gcc-11-lkftconfig-debug
>    - build-gcc-11-lkftconfig-libgpiod
>    - build-gcc-11-lkftconfig-debug-kmemleak
>    - build-clang-14-lkftconfig
>    - build-clang-nightly-lkftconfig
>    - build-gcc-11-lkftconfig
>    - build-gcc-11-lkftconfig-kasan
>    - build-clang-12-lkftconfig
>    - build-gcc-11-lkftconfig-kselftest-kernel
>    - build-gcc-11-lkftconfig-rcutorture
>    - build-gcc-11-lkftconfig-armv8_features
>    - build-gcc-11-lkftconfig-kselftest
> 
> Build: https://builds.tuxbuild.com/2F1cW8NpQ0Z6l9h9rfkZT5AXzqg/
> config: https://builds.tuxbuild.com/2F1cW8NpQ0Z6l9h9rfkZT5AXzqg/config
> 
> 
> --
> Linaro LKFT
> https://lkft.linaro.org
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2022-09-20 13:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-20 11:39 Naresh Kamboju
2022-09-20 13:50 ` James Clark [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=7dbf6fc6-5cd5-4493-af55-6ebf6b97a019@arm.com \
    --to=james.clark@arm.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=coresight@lists.linaro.org \
    --cc=leo.yan@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=mike.leach@linaro.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=suzuki.poulose@arm.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
all inboxes | Powered by JetHome®