From: Andreas Schwab <schwab@linux-m68k.org>
To: 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: {standard input}:3978: Error: value 178 out of range
Date: Fri, 10 Jun 2022 11:47:50 +0200 [thread overview]
Message-ID: <87wndoalyx.fsf@igel.home> (raw)
In-Reply-To: <CAMuHMdVGdzkaT=SR2OWoN9S=Xr-2Ckki41P_p7t4WDgRLzfuGg@mail.gmail.com> (Geert Uytterhoeven's message of "Fri, 10 Jun 2022 10:46:21 +0200")
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.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2022-06-10 9:48 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 [this message]
2022-06-10 11:16 ` [kbuild-all] " Chen, Rong A
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=87wndoalyx.fsf@igel.home \
--to=schwab@linux-m68k.org \
--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=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).