Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1498442

Re: [GIT pull] locking fix for 4.9

From Linus Torvalds <torvalds@linux-foundation.org>
Newsgroups linux.kernel
Subject Re: [GIT pull] locking fix for 4.9
Date 2016-10-10 19:30 +0200
Message-ID <sqMyK-412-29@gated-at.bofh.it> (permalink)
References <spZeF-79g-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Sat, Oct 8, 2016 at 5:47 AM, Thomas Gleixner <tglx@linutronix.de> wrote:
>
> A single fix which prevents newer GCCs from spamming the build output with
> overly eager warnings about __builtin_return_address() uses which are
> correct.

Ugh. This feels over-engineered to me.

We already disable that warning unconditionally for the trace
subdirectory, and for mm/usercopy.c.

I feel that the simpler solution is to just disable the warning
globally, and not worry about "when this config option is enabled we
need to disable it".

Basically, we disable the warning every time we ever use
__builtin_return_address(), so maybe we should just disable it once
and for all.

It's not like the __builtin_return_address() warning is so incredibly
useful anyway.

Hmm?

                Linus

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[GIT pull] locking fix for 4.9 Thomas Gleixner <tglx@linutronix.de> - 2016-10-08 14:50 +0200
  Re: [GIT pull] locking fix for 4.9 Linus Torvalds <torvalds@linux-foundation.org> - 2016-10-10 19:30 +0200
    Re: [GIT pull] locking fix for 4.9 Steven Rostedt <rostedt@goodmis.org> - 2016-10-12 10:30 +0200
      Re: [GIT pull] locking fix for 4.9 Linus Torvalds <torvalds@linux-foundation.org> - 2016-10-12 19:30 +0200
        Re: [GIT pull] locking fix for 4.9 Steven Rostedt <rostedt@goodmis.org> - 2016-10-13 03:00 +0200

csiph-web