UPSTREAM: env: suppress a spurious warning with GCC 7.1

GCC 7.1 seems to be smart enough to track val through the various
static inline functions, but not smart enough to see that val will
always be initialised when no error is returned.  This triggers
the following warning:
  env/mmc.c: In function 'mmc_get_env_addr':
  env/mmc.c:121:12: warning: 'val' may be used uninitialized in this function [-Wmaybe-uninitialized]

To make it easier for compiler to understand what is going on, let's
initialise val.

Change-Id: I9e78b4a72f8124bde37946aaad0caa82c064ec70
Signed-off-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
(cherry picked from commit fd374665c9b724bb3eb0da32db0bb7ecc5cf1337)
This commit is contained in:
Philipp Tomsich 2017-11-21 23:29:40 +01:00 committed by Kever Yang
parent 1759abcc94
commit 4c0727fd0e
1 changed files with 1 additions and 1 deletions

2
env/mmc.c vendored
View File

@ -73,7 +73,7 @@ static inline s64 mmc_offset(int copy)
.partition = "u-boot,mmc-env-partition",
.offset = "u-boot,mmc-env-offset",
};
s64 val, defvalue;
s64 val = 0, defvalue;
const char *propname;
const char *str;
int err;