From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: "the arch/x86 maintainers" <x86@kernel.org>,
"James E.J. Bottomley" <jejb@parisc-linux.org>,
Helge Deller <deller@gmx.de>
Subject: Re: Build regressions/improvements in v4.17-rc1
Date: Mon, 16 Apr 2018 15:15:56 +0200 [thread overview]
Message-ID: <CAMuHMdVKszYm5jH+o8iLdBdPTcsnpUr3rs4Z3kPtKXXH4fs8fw@mail.gmail.com> (raw)
In-Reply-To: <1523884165-17044-1-git-send-email-geert@linux-m68k.org>
On Mon, Apr 16, 2018 at 3:09 PM, Geert Uytterhoeven
<geert@linux-m68k.org> wrote:
> Below is the list of build error/warning regressions/improvements in
> v4.17-rc1[1] compared to v4.16[2].
>
> Summarized:
> - build errors: +2/-10
> - build warnings: +1407/-1867
>
> Note that there may be false regressions, as some logs are incomplete.
> Still, they're build errors/warnings.
>
> Happy fixing! ;-)
>
> Thanks to the linux-next team for providing the build service.
>
> [1] http://kisskb.ellerman.id.au/kisskb/head/60cc43fc888428bb2f18f08997432d426a243338/ (244 out of 246 configs)
> [2] http://kisskb.ellerman.id.au/kisskb/head/0adb32858b0bddf4ada5f364a84ed60b196dbcda/ (all 246 configs)
>
>
> *** ERRORS ***
>
> 2 error regressions:
> + /kisskb/src/include/linux/thread_info.h: error: call to '__bad_copy_from' declared with attribute error: copy source size is too small: => 138:19
i386-allmodconfig
> + error: No rule to make target arch/parisc/kernel/binfmt_elf32.o: => N/A
parisc64/a500_defconfig (patch available)
> *** WARNINGS ***
>
> [Deleted 799 lines about "warning: ... [-Wpointer-sign]" on parisc-allmodconfig]
> [Deleted 1480 lines about "warning: -ffunction-sections disabled; it makes profiling impossible [enabled by default]" on parisc-allmodconfig]
BTW, are there any plans to fix/silence these warrnings?
Or should I look into automating their removal from the logs/report
(optimistic me keeps on postponing that task :-)?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2018-04-16 13:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 13:09 Build regressions/improvements in v4.17-rc1 Geert Uytterhoeven
2018-04-16 13:15 ` Geert Uytterhoeven [this message]
2018-08-06 10:39 ` Geert Uytterhoeven
2018-08-06 22:54 ` Andrew Morton
[not found] ` <87lg9hb12y.fsf@concordia.ellerman.id.au>
2018-08-08 11:46 ` Mathieu Malaterre
2018-08-08 12:26 ` Geert Uytterhoeven
2018-08-08 13:16 ` Michael Ellerman
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=CAMuHMdVKszYm5jH+o8iLdBdPTcsnpUr3rs4Z3kPtKXXH4fs8fw@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=deller@gmx.de \
--cc=jejb@parisc-linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).