From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Rong Chen <rong.a.chen@intel.com>
Cc: Oliver Hartkopp <socketcan@hartkopp.net>,
kernel test robot <lkp@intel.com>,
kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
linux-can <linux-can@vger.kernel.org>
Subject: Re: [kbuild-all] Re: include/linux/compiler_types.h:315:38: error: call to '__compiletime_assert_536' declared with attribute error: BUILD_BUG_ON failed: offsetof(struct can_frame, len) != offsetof(struct canfd_frame, len) || offsetof(struct can_frame, data) != offsetof(struc...
Date: Tue, 23 Mar 2021 08:34:37 +0100 [thread overview]
Message-ID: <20210323073437.yo63wreqnubbeqby@pengutronix.de> (raw)
In-Reply-To: <b10903ca-c424-b305-d981-fe0004500190@intel.com>
[-- Attachment #1: Type: text/plain, Size: 623 bytes --]
On 23.03.2021 10:54:40, Rong Chen wrote:
> I tried arm-linux-gnueabi (gcc version 10.2.0) and the problem still
> exists, btw we prefer to not use the latest gcc compiler to avoid
> false positives.
FWIW:
I'm using latest debian arm compiler and the BUILD_BUG never triggered.
gcc version 10.2.1 20210110 (Debian 10.2.1-6)
regards,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung West/Dortmund | Phone: +49-231-2826-924 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-03-23 7:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202103210435.I0fiBGAC-lkp@intel.com>
[not found] ` <dad98ebd-77a4-3305-e681-278cabe38793@hartkopp.net>
[not found] ` <7f4f7e1c-194b-a903-d474-e3b742556a55@intel.com>
2021-03-22 16:24 ` [kbuild-all] Re: include/linux/compiler_types.h:315:38: error: call to '__compiletime_assert_536' declared with attribute error: BUILD_BUG_ON failed: offsetof(struct can_frame, len) != offsetof(struct canfd_frame, len) || offsetof(struct can_frame, data) != offsetof(struc Oliver Hartkopp
2021-03-23 2:54 ` Rong Chen
2021-03-23 5:46 ` Vincent MAILHOL
2021-03-23 6:06 ` Rong Chen
2021-03-23 7:26 ` Patrick Menschel
2021-03-23 7:34 ` Marc Kleine-Budde [this message]
2021-03-23 7:45 ` Oliver Hartkopp
2021-03-23 8:32 ` Oliver Hartkopp
2021-03-23 8:54 ` Marc Kleine-Budde
2021-03-23 8:59 ` Rong Chen
2021-03-23 11:36 ` Rasmus Villemoes
2021-03-23 12:49 ` Oliver Hartkopp
2021-03-23 14:00 ` Rasmus Villemoes
2021-03-23 18:59 ` Oliver Hartkopp
2021-03-23 20:54 ` Rasmus Villemoes
2021-03-24 9:09 ` Oliver Hartkopp
2021-03-24 9:57 ` Marc Kleine-Budde
2021-03-29 7:01 ` Marc Kleine-Budde
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=20210323073437.yo63wreqnubbeqby@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=rong.a.chen@intel.com \
--cc=socketcan@hartkopp.net \
/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).