aboutsummaryrefslogtreecommitdiff
path: root/gdb/remote.h
diff options
context:
space:
mode:
authorTom Tromey <tom@tromey.com>2018-08-15 10:05:01 -0600
committerTom Tromey <tom@tromey.com>2018-08-15 10:05:01 -0600
commit495143533ad95369811391c6e3c6dadd69d7dd67 (patch)
tree6aae28d0673ec4e53227477baaa18a733b180ee6 /gdb/remote.h
parent07aff30e92ead6c6d662462efc6ebdf83c6b8de3 (diff)
downloadgdb-495143533ad95369811391c6e3c6dadd69d7dd67.zip
gdb-495143533ad95369811391c6e3c6dadd69d7dd67.tar.gz
gdb-495143533ad95369811391c6e3c6dadd69d7dd67.tar.bz2
Use pulongest in aarch64-linux-tdep.c
While testing a patch on the buildbot, I got this error: ../../binutils-gdb/gdb/aarch64-linux-tdep.c: In function uint64_t aarch64_linux_core_read_vq(gdbarch*, bfd*): ../../binutils-gdb/gdb/aarch64-linux-tdep.c:285:29: error: format %ld expects argument of type long int, but argument 2 has type uint64_t {aka long long unsigned int} [-Werror=format=] This patch avoids the problem by using pulongest rather than %ld. This seems safe to me because, if aarch64-linux-tdep.c is included in the build, then ULONGEST must be a 64-bit type. gdb/ChangeLog 2018-08-15 Tom Tromey <tom@tromey.com> * aarch64-linux-tdep.c (aarch64_linux_core_read_vq): Use pulongest.
Diffstat (limited to 'gdb/remote.h')
0 files changed, 0 insertions, 0 deletions