From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org,
linux-parisc <linux-parisc@vger.kernel.org>,
regressions@lists.linux.dev
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Helge Deller <deller@gmx.de>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
John David Anglin <dave.anglin@bell.net>
Subject: parisc: bug.h:71:17: error: invalid 'asm': operand number out of range
Date: Mon, 27 Nov 2023 14:27:40 +0530 [thread overview]
Message-ID: <CA+G9fYsM4Aa1smp2Xahf=z2WOGpXsAC3GzUW06HJN9pucm837Q@mail.gmail.com> (raw)
The parisc tinyconfig built with gcc-11 failed on mainline v6.7-rc3.
git_describe: v6.7-rc3
git_repo: https://gitlab.com/Linaro/lkft/mirrors/torvalds/linux-mainline
parisc:
build:
* gcc-11-tinyconfig
In file included from lib/math/int_log.c:14:
lib/math/int_log.c: In function 'intlog2':
arch/parisc/include/asm/bug.h:71:17: error: invalid 'asm': operand
number out of range
71 | asm volatile("\n"
\
| ^~~
Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
Links:
- https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.7-rc3/testrun/21323529/suite/build/test/gcc-11-tinyconfig/log
- https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.7-rc3/testrun/21323529/suite/build/test/gcc-11-tinyconfig/history/
- https://storage.tuxsuite.com/public/linaro/lkft/builds/2Yk9c7RsS6V5pdDdOYzHSrlpZQk/
--
Linaro LKFT
https://lkft.linaro.org
next reply other threads:[~2023-11-27 8:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 8:57 Naresh Kamboju [this message]
2023-11-27 9:20 ` parisc: bug.h:71:17: error: invalid 'asm': operand number out of range Linux regression tracking (Thorsten Leemhuis)
2023-11-27 10:00 ` Helge Deller
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+G9fYsM4Aa1smp2Xahf=z2WOGpXsAC3GzUW06HJN9pucm837Q@mail.gmail.com' \
--to=naresh.kamboju@linaro.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=dave.anglin@bell.net \
--cc=deller@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=regressions@lists.linux.dev \
--cc=torvalds@linux-foundation.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).