aboutsummaryrefslogtreecommitdiff
path: root/bfd/elf64-gen.c
diff options
context:
space:
mode:
authorSimon Marchi <simon.marchi@efficios.com>2020-03-11 15:15:12 -0400
committerSimon Marchi <simon.marchi@efficios.com>2020-03-11 15:15:12 -0400
commita0761e34f054767de6d6389929d27e9015fb299b (patch)
treede8062143b2fecd54017af783ca41f6992f67577 /bfd/elf64-gen.c
parent5308d1e77167b4bb133302d7a6f66e599abee420 (diff)
downloadgdb-a0761e34f054767de6d6389929d27e9015fb299b.zip
gdb-a0761e34f054767de6d6389929d27e9015fb299b.tar.gz
gdb-a0761e34f054767de6d6389929d27e9015fb299b.tar.bz2
gdb: enable -Wmissing-prototypes warning
While compiling with clang, I noticed it didn't catch cases where my function declaration didn't match my function definition. This is normally caught by gcc with -Wmissing-declarations. On clang, this is caught by -Wmissing-prototypes instead. Note that on gcc, -Wmissing-prototypes also exists, but is only valid for C and Objective-C. It gets correctly rejected by the configure script since gcc rejects it with: cc1plus: error: command line option '-Wmissing-prototypes' is valid for C/ObjC but not for C++ -Werror So this warning flag ends up not used for gcc (which is what we want). gdb/ChangeLog: * configure: Re-generate. gdbserver/ChangeLog: * configure: Re-generate. gdbsupport/ChangeLog: * configure: Re-generate. * warning.m4: Enable -Wmissing-prototypes.
Diffstat (limited to 'bfd/elf64-gen.c')
0 files changed, 0 insertions, 0 deletions