From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 02/15] linux: disable Werror for powerpc kernels
Date: Sat, 22 Jun 2019 20:59:19 +0200 [thread overview]
Message-ID: <20190622205919.64896640@windsurf> (raw)
In-Reply-To: <20190620100725.105587-3-giulio.benetti@micronovasrl.com>
On Thu, 20 Jun 2019 12:07:12 +0200
Giulio Benetti <giulio.benetti@micronovasrl.com> wrote:
> From: Romain Naour <romain.naour@gmail.com>
>
> From patch [1] included in kernel >= 5.0:
> "The upcoming GCC 9 release extends the -Wmissing-attributes warnings
> (enabled by -Wall) to C and aliases: it warns when particular function
> attributes are missing in the aliases but not in their target.
>
> In particular, it triggers for all the init/cleanup_module
> aliases in the kernel (defined by the module_init/exit macros),
> ending up being very noisy.
>
> These aliases point to the __init/__exit functions of a module,
> which are defined as __cold (among other attributes). However,
> the aliases themselves do not have the __cold attribute.
>
> Since the compiler behaves differently when compiling a __cold
> function as well as when compiling paths leading to calls
> to __cold functions, the warning is trying to point out
> the possibly-forgotten attribute in the alias."
>
> Werror is set by default while building ppc kernel [2], but
> some warning can be introduced while building current kernel with
> newer compiler (for example building kernel 4.19 with gcc 9.1).
>
> For the same reason why we remove Werror in packages's compiler
> flags. Building with Werror is not bulletproof when we start
> using a newer compiler that introduce new warnings.
> This is the case here.
>
> Also this option is a bit strange since it's specific to ppc kernels:
> "The intention is to make it harder for people to inadvertantly
> introduce warnings in the arch/powerpc code."
> Other kernel developers on other arch may be interested by a
> similar/more generic option.
>
> So, It's clearly intended for kernel developers.
>
> Instead of backporting this patch [1] to kernel 4.19, select
> unconditionally the Kconfig option CONFIG_PPC_DISABLE_WERROR
> that allow to disable Werror.
>
> Fixes:
> https://gitlab.com/kubu93/toolchains-builder/-/jobs/205435741
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=a6e60d84989fa0e91db7f236eda40453b0e44afa
> [2] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=ba55bd74360ea4b8b95e73ed79474d37ff482b36
> [3] https://gitlab.com/bootlin/toolchains-builder
>
> Fix-suggested-by: Yann E. MORIN <yann.morin.1998@free.fr>
> Signed-off-by: Romain Naour <romain.naour@gmail.com>
> Signed-off-by: Giulio Benetti <giulio.benetti@micronovasrl.com>
> ---
> v2: add a shared fragment in board/fragments/linux and update
> qemu ppc* defconfigs. (Arnout)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-06-22 18:59 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 10:07 [Buildroot] [PATCH v4 00/15] Add gcc 9.1 Giulio Benetti
2019-06-20 10:07 ` [Buildroot] [PATCH v4 01/15] package/glibc/arc: fix build issue with gcc-9.1 Giulio Benetti
2019-06-22 18:58 ` Thomas Petazzoni
2019-06-20 10:07 ` [Buildroot] [PATCH v4 02/15] linux: disable Werror for powerpc kernels Giulio Benetti
2019-06-22 18:59 ` Thomas Petazzoni [this message]
2019-06-24 20:15 ` Peter Korsgaard
2019-06-25 3:05 ` Baruch Siach
2019-06-25 6:18 ` Peter Korsgaard
2019-06-20 10:07 ` [Buildroot] [PATCH v4 03/15] package/uclibc: remove asm constraint Giulio Benetti
2019-06-22 19:31 ` Thomas Petazzoni
2019-06-20 10:07 ` [Buildroot] [PATCH v4 04/15] toolchain: add gcc 9 entry Giulio Benetti
2019-06-22 19:39 ` Thomas Petazzoni
2019-06-20 10:07 ` [Buildroot] [PATCH v4 05/15] package/gcc: add support for gcc 9.1 Giulio Benetti
2019-06-22 19:40 ` Thomas Petazzoni
2019-06-20 10:07 ` [Buildroot] [PATCH v4 06/15] arch: add BR2_ARCH_NEEDS_GCC_AT_LEAST_9 Giulio Benetti
2019-06-22 19:41 ` Thomas Petazzoni
2019-06-23 9:26 ` Peter Korsgaard
2019-06-20 10:07 ` [Buildroot] [PATCH v4 07/15] toolchain-external: add gcc 9 entry Giulio Benetti
2019-06-22 19:42 ` Thomas Petazzoni
2019-06-20 10:07 ` [Buildroot] [PATCH v4 08/15] package/gcc: switch to gcc 8.x as the default Giulio Benetti
2019-06-22 19:44 ` Thomas Petazzoni
2019-06-22 22:35 ` Romain Naour
2019-06-23 16:21 ` Thomas Petazzoni
2019-06-24 6:35 ` Peter Korsgaard
2019-06-25 22:25 ` Arnout Vandecappelle
2019-06-26 6:55 ` Romain Naour
2019-06-26 7:23 ` Thomas Petazzoni
2019-06-26 7:34 ` Romain Naour
2019-06-26 6:55 ` Thomas Petazzoni
2019-06-23 9:29 ` Peter Korsgaard
2019-06-20 10:07 ` [Buildroot] [PATCH v4 09/15] arch/arm: move dependency on 64-bit down to individual cores Giulio Benetti
2019-07-13 21:11 ` Arnout Vandecappelle
2019-06-20 10:07 ` [Buildroot] [PATCH v4 10/15] arch/arm: some cores have a different name with gcc-9 Giulio Benetti
2019-07-13 21:13 ` Arnout Vandecappelle
2019-07-13 21:33 ` Yann E. MORIN
2019-06-20 10:07 ` [Buildroot] [PATCH v4 11/15] arch/arm: saphira is in fact an armv8.4a Giulio Benetti
2019-06-20 10:07 ` [Buildroot] [PATCH v4 12/15] arch/arm: add two new 64-bit-only armv8a cores Giulio Benetti
2019-06-20 10:07 ` [Buildroot] [PATCH v4 13/15] arch/arm: add two new cortex-based armv8.2a cores Giulio Benetti
2019-06-20 10:07 ` [Buildroot] [PATCH v4 14/15] arch/arm: add two new non-cortex-based " Giulio Benetti
2019-07-13 21:22 ` Arnout Vandecappelle
2019-07-13 21:51 ` Yann E. MORIN
2019-06-20 10:07 ` [Buildroot] [PATCH v4 15/15] package/gcc: enable gcc 9.1 for ork1 (openrisc) Giulio Benetti
2019-07-13 21:24 ` Arnout Vandecappelle
2019-07-13 23:57 ` Guo Ren
2019-07-14 8:40 ` Yann E. MORIN
2019-07-14 9:18 ` Guo Ren
2019-07-14 9:39 ` Yann E. MORIN
2019-07-14 10:00 ` Thomas Petazzoni
2019-07-14 10:08 ` Yann E. MORIN
2019-07-14 12:48 ` Romain Naour
2019-07-15 21:55 ` [Buildroot] [arc-buildroot] " Alexey Brodkin
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=20190622205919.64896640@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.