linux-kernel - Re: TRACE_BRANCH_PROFILING breaks gcc warnings

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1239748293.21121.60.camel@localhost.localdomain>
Date:	Tue, 14 Apr 2009 18:31:33 -0400
From:	Steven Rostedt <srostedt@...hat.com>
To:	Johannes Berg <johannes@...solutions.net>
Cc:	Ingo Molnar <mingo@...hat.com>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: TRACE_BRANCH_PROFILING breaks gcc warnings


On Wed, 2009-04-15 at 00:28 +0200, Johannes Berg wrote:
> With TRACE_BRANCH_PROFILING enabled you get "dummy may be used
> uninitialised" with code like the following (and gcc 4.3.3):
> 
> void *dummy, *c;
> 
> if (a && (dummy = b()))
> 	c = dummy;
> 
> Therefore, allyesconfig has become useless for looking at warnings.
> 
> :(


This has been mentioned before, and I've asked about sending a patch
that would prevent TRACE_BRANCH_PROFILING from being selected with an
allyesconfig.

It is easy to do. I could make it a selection and not a boolean and it
will not select it as default, even for allyes/modconfig

Thoughts?

-- Steve


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/