From: Guenter Roeck <linux@roeck-us.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Arnd Bergmann <arnd@arndb.de>, stable <stable@vger.kernel.org>
Subject: Re: Patches for -stable to improve support for recent gcc versions
Date: Wed, 30 May 2018 13:37:55 -0700 [thread overview]
Message-ID: <20180530203755.GA25740@roeck-us.net> (raw)
In-Reply-To: <20180530200451.GA14464@kroah.com>
On Wed, May 30, 2018 at 10:04:51PM +0200, Greg Kroah-Hartman wrote:
> On Wed, May 30, 2018 at 09:34:34PM +0200, Arnd Bergmann wrote:
> > On Wed, May 30, 2018 at 9:24 PM, Greg Kroah-Hartman
> > > Why is that not an option enabled for all arches right now for gcc-8?
> >
> > I would still want this warning enabled by default in future kernels,
> > just disabled
> > for the system call definitions (until we decide to rework the way
> > they are defined).
> >
> > What I'd suggest we do is a series of patches:
> >
> > 1. disable both -Wno-attribute-alias and -Wstringop-truncation by
> > default, but leave them
> > enabled in 'make W=1'. Mark this one for stable backports
> > 2. add a macro to let users disable warnings locally within a file,
> > based on _Pragma("GCC
> > diagnostic ...")
> > 3. change the system call macros to disable -Wno-attribute-alias inside of the
> > SYSCALL_DEFINEx() macros
> > 4. turn on -Wno-attribute-alias again by default.
>
> That sounds like a good plan to me.
>
Agreed.
Guenter
prev parent reply other threads:[~2018-05-30 20:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 13:48 Patches for -stable to improve support for recent gcc versions Guenter Roeck
2018-05-30 8:38 ` Greg Kroah-Hartman
2018-05-30 13:18 ` Guenter Roeck
2018-05-30 13:46 ` Greg Kroah-Hartman
2018-05-30 9:27 ` Arnd Bergmann
2018-05-30 9:44 ` Greg Kroah-Hartman
2018-05-30 9:52 ` Arnd Bergmann
2018-05-30 10:00 ` Greg Kroah-Hartman
2018-05-30 13:31 ` Guenter Roeck
2018-05-30 13:55 ` Arnd Bergmann
2018-05-30 18:46 ` Guenter Roeck
2018-05-30 19:24 ` Greg Kroah-Hartman
2018-05-30 19:34 ` Arnd Bergmann
2018-05-30 20:04 ` Greg Kroah-Hartman
2018-05-30 20:37 ` Guenter Roeck [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=20180530203755.GA25740@roeck-us.net \
--to=linux@roeck-us.net \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--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 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.