From: Arnd Bergmann <arnd@arndb.de>
To: Olof Johansson <olof@lixom.net>
Cc: Kernel Build Reports Mailman List
<kernel-build-reports@lists.linaro.org>,
Olof's autobuilder <build@lixom.net>,
stable <stable@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: stable-rc build: 72 warnings 1 failures (stable-rc/v4.4.30-35-gf821e08)
Date: Wed, 09 Nov 2016 01:07:29 +0100 [thread overview]
Message-ID: <4836576.1GPFp5cEvS@wuerfel> (raw)
In-Reply-To: <CAOesGMjH1jGum3E08F2h5dH2dyq_ekwZ_4M7piAdsxDFvhXu8g@mail.gmail.com>
On Tuesday, November 8, 2016 3:26:52 PM CET Olof Johansson wrote:
> On Tue, Nov 8, 2016 at 2:17 PM, Olof Johansson <olof@lixom.net> wrote:
> > On Tue, Nov 8, 2016 at 2:14 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> >> On Tuesday, November 8, 2016 9:16:28 AM CET Olof's autobuilder wrote:
> >>> Here are the build results from automated periodic testing.
> >>>
> >>> The tree being built was stable-rc, found at:
> >>>
> >>> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable-rc.git/
> >>>
> >>> Topmost commit:
> >>>
> >>> f821e08 Linux 4.4.31-rc1
> >>>
> >>> Build logs (stderr only) can be found at the following link (experimental):
> >>>
> >>> http://arm-soc.lixom.net/buildlogs/stable-rc/v4.4.30-35-gf821e08/
> >>
> >> These seem to be largely caused by building with gcc-6. It's probably
> >> a good idea to keep supporting that configuration though and
> >> backport the fixes. Here are the upstream commit IDs I've found.
> >
> > That's a lot of noise. I'll move back to build with gcc 4.9.2 instead, for now.
> >
> > It's not entirely reasonable to expect older releases to build with
> > new toolchains without warnings, and I'm not sure if it makes sense to
> > bring back those fixes to -stable (unless they fix real bugs, of
> > course).
>
> A lot less noise with older gcc:
>
> http://arm-soc.lixom.net/buildlogs/stable-rc/v4.4.30-44-gc5be865/
Out of the ones I mentioned earlier, that leaves
aaaab56dba9a ("of: silence warnings due to max() usage")
badbda53e505 ("mm/cma: silence warnings due to max() usage")
but adds a couple of others:
| arch/powerpc/relocs_check.sh: line 46: ccache /usr/local/cross-4.9.2/bin/powerpc64-linux-objdump: No such file or directory
| arch/arm64/Makefile:25: LSE atomics not supported by binutils
These seem to be caused by an older binutils release in your cross-4.9.2 build
| In file included from /work/build/batch/drivers/isdn/hardware/eicon/message.c:30:0:
| /work/build/batch/drivers/isdn/hardware/eicon/message.c: In function 'mixer_notify_update':
| /work/build/batch/drivers/isdn/hardware/eicon/platform.h:333:18: warning: array subscript is above array bounds [-Warray-bounds]
| *(__le16 *)addr = cpu_to_le16(v);
This looks like a false-positive bug caused by 4.9 that is no longer
present in newer compilers.
I assume this is the line
PUT_WORD(&(((CAPI_MSG *) msg)->info.facility_req.structs[1]), LI_REQ_SILENT_UPDATE);
Arnd
next prev parent reply other threads:[~2016-11-09 0:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5822086c.4666420a.e9479.80e9@mx.google.com>
2016-11-08 22:14 ` stable-rc build: 72 warnings 1 failures (stable-rc/v4.4.30-35-gf821e08) Arnd Bergmann
2016-11-08 22:17 ` Olof Johansson
2016-11-08 23:26 ` Olof Johansson
2016-11-09 0:07 ` Arnd Bergmann [this message]
2016-11-09 9:44 ` Greg KH
2016-11-09 10:02 ` Greg KH
2016-11-09 0:45 ` Eric W. Biederman
2016-11-09 15:44 ` Arnd Bergmann
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=4836576.1GPFp5cEvS@wuerfel \
--to=arnd@arndb.de \
--cc=build@lixom.net \
--cc=ebiederm@xmission.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=olof@lixom.net \
--cc=stable@vger.kernel.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