diff options
author | Patrick Georgi <pgeorgi@google.com> | 2021-06-14 17:12:58 +0200 |
---|---|---|
committer | Patrick Georgi <pgeorgi@google.com> | 2021-06-15 19:46:47 +0000 |
commit | a5061f8f5772e59725c8e89e02b9dff10735e915 (patch) | |
tree | 47596bde32b38c1eff00d8ed73f44b09ff53a1d6 /src/cpu/x86 | |
parent | 47ad2ae3f984ffa6fb3803bdbea6bd7d96bad819 (diff) |
tpm/tss: Remove local variable
Depending on how the "middle-end" (yes, the gcc developers are
serious about that) optimizer ends up mangling the code, there may
or may not be a complaint about x being used uninitialized when it's
clearly not used at all.
So instead, why keep x in the first place? memcpy(foo, NULL, 0) is
the same as memcpy(foo, some_uninitialized_variable, 0) in that it
does nothing.
Change-Id: Ib0a97c3e3fd1a2a6aff37da63376373c88ac595d
Signed-off-by: Patrick Georgi <pgeorgi@google.com>
Reviewed-on: https://review.coreboot.org/c/coreboot/+/55499
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Angel Pons <th3fanbus@gmail.com>
Diffstat (limited to 'src/cpu/x86')
0 files changed, 0 insertions, 0 deletions