diff options
| author | Mike Frysinger <vapier@chromium.org> | 2016-01-26 15:38:19 -0500 |
|---|---|---|
| committer | Mike Frysinger <vapier@chromium.org> | 2016-01-26 15:38:19 -0500 |
| commit | bc44efdc274aaf5b3b575d66f7e245754c0fa1e1 (patch) | |
| tree | 5215c96d8fa995f3a65f162a0a16c4dc050f1e41 /src/third_party/linux/include/gflags/gflags.h | |
| parent | autotools: regen w/latest versions (diff) | |
| download | breakpad-bc44efdc274aaf5b3b575d66f7e245754c0fa1e1.tar.xz | |
convert to uint8_t* for binary data to fix -Wnarrowing build errors
Newer gcc versions default to -Werror=narrowing when using newer C++
standards (which we do). This causes issues when we try to stuff a
value like 0xea into a char -- the value is out of range for signed
char bytes. That's when gcc throws an error:
.../bytereader_unittest.cc: In member function 'virtual void Reader_DW_EH_PE_absptr4_Test::TestBody()':
.../bytereader_unittest.cc:400:55: error: narrowing conversion of '234' from 'int' to 'char' inside { } [-Wnarrowing]
BUG=chromium:579384
TEST=`make check` passes
R=mark@chromium.org
Review URL: https://codereview.chromium.org/1605153004 .
Diffstat (limited to 'src/third_party/linux/include/gflags/gflags.h')
0 files changed, 0 insertions, 0 deletions