From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andy Shevchenko Date: Fri, 24 Nov 2017 17:56:39 +0200 Subject: [U-Boot] Intel Edison build warning In-Reply-To: <1511538142.25007.441.camel@linux.intel.com> References: <1511538142.25007.441.camel@linux.intel.com> Message-ID: <1511538999.25007.444.camel@linux.intel.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Fri, 2017-11-24 at 17:42 +0200, Andy Shevchenko wrote: > On Fri, 2017-11-24 at 16:06 +0800, Bin Meng wrote: > > Hi, > > > > Intel Edison has a build warning below. > > > > + *env_addr = offset; > > + ^ > > w+../env/mmc.c: In function 'mmc_get_env_addr': > > w+../env/mmc.c:121:12: warning: 'val' may be used uninitialized in > > this function [-Wmaybe-uninitialized] > > > > I did not figure out what is wrong here. v2017.11 does not have such > > build warning. > > > > Do you have any idea? Somewhat compiler goes crazy? I have a theory that instead of showing actual potential issues (which are bogus anyway) it complains on __weak function instead. The real complains might be env_mmc_load() / env_mmc_save() where offset* is uninitialized indeed. -- Andy Shevchenko Intel Finland Oy