From: Helge Deller <deller@gmx.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Michael Ellerman <mpe@ellerman.id.au>
Cc: Parisc List <linux-parisc@vger.kernel.org>
Subject: Re: Build regressions/improvements in v4.6-rc4 (parisc warnings)
Date: Tue, 19 Apr 2016 15:31:59 +0200 [thread overview]
Message-ID: <5716334F.6020602@gmx.de> (raw)
In-Reply-To: <CAMuHMdUqJ0dj25oXhC4MgqSk0SaOHvT262ew+sBs7eV2SCwyUA@mail.gmail.com>
Hi Geert,
On 19.04.2016 08:57, Geert Uytterhoeven wrote:
> On Tue, Apr 19, 2016 at 8:53 AM, Geert Uytterhoeven
> <geert@linux-m68k.org> wrote:
>> Below is the list of build error/warning regressions/improvements in
>> v4.6-rc4[1] compared to v4.5[2].
>>
>> Summarized:
>> - build errors: +11/-7
>> - build warnings: +16376/-165 <tel:+16376165>
>
> Sorry for the delay, initially I didn't realize why my first report didn't make
> it to the list. It was too big, due to 16211 warnings in parisc-allmodconfig
> about "-ffunction-sections disabled; it makes profiling impossible [enabled by
> default]".
I checked the parisc warnings, and looking at http://kisskb.ellerman.id.au/kisskb/buildresult/12665382/
it seems a gcc-4.6 (/opt/cross/gcc-4.6.3-nolibc/hppa-linux/bin/hppa-linux-gcc) compiler
is still being used.
I tend to think, that gcc-4.6 wasn't able to generate function sections
which is why we see those warnings now (there was a FTRACE patch from me
included before v4.6-rc4).
Anyway, I can't reproduce those warnings with gcc-4.8 and higher.
Given the fact, that we even switched on debian now to use gcc-5 for the kernel, can
someone please update the 32- and 64-bit parisc compilers on the kiss
infrastructure to at least gcc-4.8 (gcc-4.9 or gcc-5 being preferred).
Thanks,
Helge
prev parent reply other threads:[~2016-04-19 13:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 6:53 Build regressions/improvements in v4.6-rc4 Geert Uytterhoeven
2016-04-19 6:57 ` Geert Uytterhoeven
2016-04-19 13:31 ` Helge Deller [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=5716334F.6020602@gmx.de \
--to=deller@gmx.de \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=mpe@ellerman.id.au \
/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).