Tidy check_uvalue
authorAlan Modra <amodra@gmail.com>
Wed, 28 Aug 2019 23:34:08 +0000 (09:04 +0930)
committerAlan Modra <amodra@gmail.com>
Wed, 28 Aug 2019 23:34:35 +0000 (09:04 +0930)
commita85eba51f619d3e8c813a12871172f23689b28d6
tree2e1ecfbaf00869124544c05344e2d07d201a4618
parent83cf0d04dcdc9a4e7f105a517390e4c1af444340
Tidy check_uvalue

I don't see a need to calculate "ptr = start + uvalue" then compare
"ptr" with "start" and "end".  Given "start <= end" on entry, the
"uvalue" comparison with "max_uvalue" ought to be sufficient to ensure
"start + uvalue" is bounded by "start" and "end" regardless of the
size of pointers and the unsigned dwarf_vma integer type.

* dwarf.c (check_uvalue): Remove unnecessary pointer checks.
binutils/ChangeLog
binutils/dwarf.c