From: Ladislav Michl <ladis@triops.cz>
To: Naresh Kamboju <naresh.kamboju@linaro.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
linux-usb@vger.kernel.org, linux-mips@vger.kernel.org,
lkft-triage@lists.linaro.org
Cc: Thinh.Nguyen@synopsys.com,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Arnd Bergmann <arnd@arndb.de>,
Anders Roxell <anders.roxell@linaro.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Subject: Re: next: mips: cavium_octeon_defconfig: gcc-8 - dwc3-octeon.c:502:8: include/linux/compiler_types.h:397:38: error: call to '__compiletime_assert_335' declared with attribute error: FIELD_PREP: value too large for the field _compiletime_assert
Date: Tue, 08 Aug 2023 09:45:25 +0200 [thread overview]
Message-ID: <1ab766fca893588d75590d2faf624eb7d9d27a8a.camel@triops.cz> (raw)
In-Reply-To: <CA+G9fYspyEdT9wmVpL04J-p0CwqA+_v_L4H+ihY9VYqpCMmQ1Q@mail.gmail.com>
Hi Naresh,
On Tue, 2023-08-08 at 12:41 +0530, Naresh Kamboju wrote:
> [My two cents]
>
> While building Linux next-20230808 mips cavium_octeon_defconfig with
> gcc-8
> failed with below warnings and errors.
>
> Build log:
> ----------
>
> In function 'dwc3_octeon_setup.isra.4',
> inlined from 'dwc3_octeon_probe' at drivers/usb/dwc3/dwc3-
> octeon.c:502:8:
> include/linux/compiler_types.h:397:38: error: call to
> '__compiletime_assert_335' declared with attribute error: FIELD_PREP:
> value too large for the field
> _compiletime_assert(condition, msg, __compiletime_assert_,
> __COUNTER__)
> ^
> include/linux/compiler_types.h:378:4: note: in definition of macro
> '__compiletime_assert'
> prefix ## suffix(); \
> ^~~~~~
Not sure what is really going on there. Code compiles even using 32bit
toochains without warnings and such an assignments are used in other
kernel drivers. See for example drivers/cxl/core/hdm.c:534 which is
using the same types. Also
drivers/net/ethernet/marvell/octeontx2/af/rvu_npc_hash.c in
rvu_exact_prepare_table_entry...
Anyway, let me setup gcc-8 toolchain :)
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> Links:
> -----
> -
> https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20230808/testrun/18882876/suite/build/test/gcc-8-cavium_octeon_defconfig/log
> -
> https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20230808/testrun/18882876/suite/build/test/gcc-8-cavium_octeon_defconfig/history/
>
> Steps to reproduce:
> ------------
> tuxmake --runtime podman --target-arch mips --toolchain gcc-8
> --kconfig cavium_octeon_defconfig
> -
> https://storage.tuxsuite.com/public/linaro/lkft/builds/2TgoAZwerJ28UWHyqfQUiaYYhrl/tuxmake_reproducer.sh
>
> --
> Linaro LKFT
> https://lkft.linaro.org
next prev parent reply other threads:[~2023-08-08 18:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 7:11 next: mips: cavium_octeon_defconfig: gcc-8 - dwc3-octeon.c:502:8: include/linux/compiler_types.h:397:38: error: call to '__compiletime_assert_335' declared with attribute error: FIELD_PREP: value too large for the field _compiletime_assert Naresh Kamboju
2023-08-08 7:45 ` Ladislav Michl [this message]
2023-08-08 9:10 ` Ladislav Michl
2023-08-09 6:29 ` Naresh Kamboju
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=1ab766fca893588d75590d2faf624eb7d9d27a8a.camel@triops.cz \
--to=ladis@triops.cz \
--cc=Thinh.Nguyen@synopsys.com \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=tsbogend@alpha.franken.de \
/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).