aboutsummaryrefslogtreecommitdiff
path: root/gdb/memory-map.c
diff options
context:
space:
mode:
authorTom Tromey <tom@tromey.com>2018-08-07 12:48:47 -0600
committerTom Tromey <tom@tromey.com>2018-08-27 12:00:09 -0600
commit70ab8ccd4f382a6c7e59c523c22b07fe03a95f52 (patch)
treead5acd6eef8ceb059deb909d944f39d21d9471b5 /gdb/memory-map.c
parent896a7aa6a119ce9d4872de87dabb81176489b1a3 (diff)
downloadgdb-70ab8ccd4f382a6c7e59c523c22b07fe03a95f52.zip
gdb-70ab8ccd4f382a6c7e59c523c22b07fe03a95f52.tar.gz
gdb-70ab8ccd4f382a6c7e59c523c22b07fe03a95f52.tar.bz2
Use CORE_ADDR_MAX in various "breaks" arrays
Code like this: CORE_ADDR breaks[2] = {-1, -1}; ... gives a warning with -Wnarrowing. This patch changes all instances of this to use CORE_ADDR_MAX instead. gdb/ChangeLog 2018-08-27 Tom Tromey <tom@tromey.com> * rs6000-tdep.c (ppc_deal_with_atomic_sequence): Use CORE_ADDR_MAX. * mips-tdep.c (mips_deal_with_atomic_sequence) (micromips_deal_with_atomic_sequence): Use CORE_ADDR_MAX. * arch/arm-get-next-pcs.c (thumb_deal_with_atomic_sequence_raw) (arm_deal_with_atomic_sequence_raw): Use CORE_ADDR_MAX. * alpha-tdep.c (alpha_deal_with_atomic_sequence): Use CORE_ADDR_MAX. * aarch64-tdep.c (aarch64_software_single_step): Use CORE_ADDR_MAX.
Diffstat (limited to 'gdb/memory-map.c')
0 files changed, 0 insertions, 0 deletions