From: Philip Li <philip.li@intel.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: kbuild test robot <lkp@intel.com>,
kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: Re: [kbuild-all] Re: {standard input}:211: Error: operand out of range (128 is not between -128 and 127)
Date: Sun, 1 Dec 2019 10:41:50 +0800 [thread overview]
Message-ID: <20191201024150.GA24494@intel.com> (raw)
In-Reply-To: <20191201012423.GK20752@bombadil.infradead.org>
On Sat, Nov 30, 2019 at 05:24:23PM -0800, Matthew Wilcox wrote:
> On Sun, Dec 01, 2019 at 08:53:31AM +0800, kbuild test robot wrote:
> > FYI, the error/warning still remains.
> >
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > head: 32ef9553635ab1236c33951a8bd9b5af1c3b1646
> > commit: 5a74ac4c4a97bd8b7dba054304d598e2a882fea6 idr: Fix idr_get_next_ul race with idr_remove
> > date: 4 weeks ago
> > config: arc-defconfig (attached as .config)
> > compiler: arc-elf-gcc (GCC) 7.4.0
>
> Still don't care. You need to drop this broken compiler from your test cases.
sorry for this, we will blacklist it. And we will upgrade compiler to gcc-7.5
firstly to see whether there're bug fixes at compiler side.
> _______________________________________________
> kbuild-all mailing list -- kbuild-all@lists.01.org
> To unsubscribe send an email to kbuild-all-leave@lists.01.org
next prev parent reply other threads:[~2019-12-01 2:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-01 0:53 {standard input}:211: Error: operand out of range (128 is not between -128 and 127) kbuild test robot
[not found] ` <CAD9cdQ7+BtONYX-HUXYE1k2wRYAeccjAgjSA9MPqXJUTK03pUg@mail.gmail.com>
[not found] ` <CAD9cdQ44G0BeH8tnb8yPXuLBGonMT2RM6gu0fk_awB73WrvQgw@mail.gmail.com>
[not found] ` <CAD9cdQ7hTr2T-Gm91CB=0wv=FhgEQdm+JSmyNamP7J9NdkmTNQ@mail.gmail.com>
2019-12-01 1:03 ` Rainer Sickinger
2019-12-01 1:24 ` Matthew Wilcox
2019-12-01 2:41 ` Philip Li [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-11-20 10:31 kbuild test robot
2019-11-20 12:30 ` Matthew Wilcox
2019-11-25 0:57 ` [kbuild-all] " Rong Chen
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=20191201024150.GA24494@intel.com \
--to=philip.li@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=willy@infradead.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 NNTP newsgroup(s).