From: "Chen, Rong A" <rong.a.chen@intel.com>
To: Andreas Schwab <schwab@linux-m68k.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: kernel test robot <lkp@intel.com>,
Sumit Saxena <sumit.saxena@broadcom.com>,
kbuild-all@lists.01.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Himanshu Madhani <himanshu.madhani@oracle.com>,
linux-m68k <linux-m68k@lists.linux-m68k.org>
Subject: Re: [kbuild-all] Re: {standard input}:3978: Error: value 178 out of range
Date: Fri, 10 Jun 2022 19:16:46 +0800 [thread overview]
Message-ID: <2698711f-aaf6-bfc4-9b4f-b49d6acf3a32@intel.com> (raw)
In-Reply-To: <87wndoalyx.fsf@igel.home>
On 6/10/2022 5:47 PM, Andreas Schwab wrote:
> On Jun 10 2022, Geert Uytterhoeven wrote:
>
>> The offending instruction is:
>>
>> | drivers/scsi/mpi3mr/mpi3mr_fw.c:299: switch (host_tag) {
>> mvz.w %d2,%d0 | tmp160, host_tag
>> mov3q.l #5,%d1 |,
>> cmp.l %d0,%d1 | host_tag,
>> jcs .L154 |
>> tst.w %d6 | host_tag
>> jeq .L133 |
>> subq.l #2,%d2 |, tmp238
>> mvz.w %d2,%d2 | tmp238, tmp240
>> mov3q.l #3,%d0 |,
>> cmp.l %d2,%d0 | tmp240,
>> jcs .L140 |
>> add.l %d2,%d2 | tmp244
>>>>> move.w .L155(%pc,%d2.l),%d0 |, tmp245
>> jra .L186 |
>>
>> And the table L155 is just too far from the above instruction, so
>> the displacement is too large, causing the failure.
>>
>> Looks like a compiler bug to me?
>
> Yes, it's https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104028.
>
Thanks for the information, we have added the commit 43ca110050
to ignore list to avoid reporting it again.
Best Regards,
Rong Chen
prev parent reply other threads:[~2022-06-10 11:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 0:42 {standard input}:3978: Error: value 178 out of range kernel test robot
2022-06-10 8:46 ` Geert Uytterhoeven
2022-06-10 9:47 ` Andreas Schwab
2022-06-10 11:16 ` Chen, Rong A [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=2698711f-aaf6-bfc4-9b4f-b49d6acf3a32@intel.com \
--to=rong.a.chen@intel.com \
--cc=geert@linux-m68k.org \
--cc=himanshu.madhani@oracle.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=lkp@intel.com \
--cc=martin.petersen@oracle.com \
--cc=schwab@linux-m68k.org \
--cc=sumit.saxena@broadcom.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).