linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Bart Van Assche <bvanassche@acm.org>
Cc: open list <linux-kernel@vger.kernel.org>,
	linux-scsi@vger.kernel.org,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Avri Altman <avri.altman@wdc.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Anders Roxell <anders.roxell@linaro.org>
Subject: Re: next: arm64: gcc-8-defconfig: ufshcd.c:10629:2: /builds/linux/include/linux/compiler_types.h:397:38: error: call to '__compiletime_assert_553' declared with attribute error: BUILD_BUG_ON failed:
Date: Tue, 1 Aug 2023 19:53:37 +0530	[thread overview]
Message-ID: <CA+G9fYsYifn9ywPc8KqYHwDDSTRQGOgf_T58Gpt9CYDBs8u+SQ@mail.gmail.com> (raw)
In-Reply-To: <a660adba-b73b-1c02-f642-c287bb4c72fc@acm.org>

On Tue, 1 Aug 2023 at 18:53, Bart Van Assche <bvanassche@acm.org> wrote:
>
> On 8/1/23 05:16, Naresh Kamboju wrote:
> > Following build error noticed while building Linux next-20230801 tag
> > arm64 defconfig with gcc-8 toolchain.
> >
> > Regressions found on arm64:
> >
> >    - build/gcc-8-defconfig
> >    - build/gcc-8-defconfig-40bc7ee5
> >
> >
> > Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> >
> > log:
> > -----
> > In function 'ufshcd_check_header_layout',
> >      inlined from 'ufshcd_core_init' at
> > /builds/linux/drivers/ufs/core/ufshcd.c:10629:2:
> > /builds/linux/include/linux/compiler_types.h:397:38: error: call to
> > '__compiletime_assert_553' declared with attribute error: BUILD_BUG_ON
> > failed: ((u8 *)&(struct request_desc_header){ .enable_crypto = 1})[2]
> > != 0x80
> >    _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
> >                                        ^
> >
> >
> > Links:
> >   - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20230801/testrun/18754886/suite/build/test/gcc-8-defconfig/log
> >   - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20230801/testrun/18754886/suite/build/test/gcc-8-defconfig/details/
> >   - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20230801/testrun/18754886/suite/build/test/gcc-8-defconfig/history/
>
> I can't reproduce this build error with a gcc-12 arm64 cross-compiler. How
> important is gcc-8 for the ARM community?

You are right,
gcc-12 build pass.
gcc-8 build failed.


If you want to reproduce with gcc-8 you may follow these steps.

# To install tuxmake to your home directory at ~/.local/bin:
# pip3 install -U --user tuxmake
#
# Or install a deb/rpm depending on the running distribution
# See https://tuxmake.org/install-deb/ or
# https://tuxmake.org/install-rpm/
#
# See https://docs.tuxmake.org/ for complete documentation.
# Original tuxmake command with fragments listed below.
# tuxmake --runtime podman --target-arch arm64 --toolchain gcc-8
--kconfig defconfig


tuxmake --runtime podman --target-arch arm64 --toolchain gcc-8
--kconfig https://storage.tuxsuite.com/public/linaro/lkft/builds/2TN3A8EaWQJAcOYnbXZnkb7D3H7/config

>
> Thanks,
>
> Bart.

- Naresh

  reply	other threads:[~2023-08-01 14:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-01 12:16 next: arm64: gcc-8-defconfig: ufshcd.c:10629:2: /builds/linux/include/linux/compiler_types.h:397:38: error: call to '__compiletime_assert_553' declared with attribute error: BUILD_BUG_ON failed: Naresh Kamboju
2023-08-01 13:23 ` Bart Van Assche
2023-08-01 14:23   ` Naresh Kamboju [this message]
2023-08-01 14:56     ` Arnd Bergmann
2023-08-01 17:51       ` Bart Van Assche
2023-08-01 19:54         ` Arnd Bergmann
2023-08-01 20:15           ` Bart Van Assche

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=CA+G9fYsYifn9ywPc8KqYHwDDSTRQGOgf_T58Gpt9CYDBs8u+SQ@mail.gmail.com \
    --to=naresh.kamboju@linaro.org \
    --cc=anders.roxell@linaro.org \
    --cc=arnd@arndb.de \
    --cc=avri.altman@wdc.com \
    --cc=bvanassche@acm.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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).