From mboxrd@z Thu Jan 1 00:00:00 1970 From: arnd@arndb.de (Arnd Bergmann) Date: Fri, 12 Feb 2016 23:18:56 +0100 Subject: [PATCH] branch tracer: fix freak link error In-Reply-To: <20160212171237.22d2d93e@gandalf.local.home> References: <1455312410-1058841-1-git-send-email-arnd@arndb.de> <6132207.AQ6oOdTfsj@wuerfel> <20160212171237.22d2d93e@gandalf.local.home> Message-ID: <2986179.BoCBGAiP5D@wuerfel> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Friday 12 February 2016 17:12:37 Steven Rostedt wrote: > On Fri, 12 Feb 2016 22:52:10 +0100 > Arnd Bergmann wrote: > > > On Friday 12 February 2016 22:49:07 Arnd Bergmann wrote: > > > Now I have to check if it does anything to the spurious "maybe-uninitialized" > > > warnings that I saw creeping in with PROFILE_ALL_BRANCHES. My guess is > > > that it doesn't fix them (I submitted a patch to turn off those > > > warnings today when PROFILE_ALL_BRANCHES is set), but I'll try anyway. > > > > Ok, that was easy: they are all still there, so we still need to > > pass -Wno-maybe-uninitialized when using PROFILE_ALL_BRANCHES to > > avoid flooding the log with useless warnings. > > Yeah, those warnings were the reason I turned PROFILE_ALL_BRANCHES into > a tristate and not a boolean, otherwise a make allmodconfig or > allyesconfig would enable it and spam the compile with those warnings. > > I simply ignore them, so adding a way to turn them off when that is > enabled is probably a good idea. Ok. The series I sent today was titled "[PATCH 0/5] gcov fixes and maybe-uninitialized warnings", and I disable the warnings for both GCOV_PROFILE_ALL and PROFILE_ALL_BRANCHES there, along with CC_OPTIMIZE_FOR_SIZE and UBSAN_SANITIZE_ALL that already do that today. The patch series also makes sure that all four options are disabled in allmodconfig (today they are disabled because of CC_OPTIMIZE_FOR_SIZE) and the remaining warnings I get in both allmodconfig and randconfig are finally useful. Arnd