Don't use gdb_py_long_from_longest
authorTom Tromey <tromey@adacore.com>
Tue, 15 Sep 2020 17:08:56 +0000 (11:08 -0600)
committerTom Tromey <tromey@adacore.com>
Tue, 15 Sep 2020 17:08:56 +0000 (11:08 -0600)
commit4bde49dc81c5c16189af70b9a144dbb5651994f1
tree538a8007afa184fc28f2f9a5781265afc1402156
parent37431074656958dfb788a1980f5a1cd474705b83
Don't use gdb_py_long_from_longest

Change the Python layer to avoid gdb_py_long_from_longest, and remove
the defines.

gdb/ChangeLog
2020-09-15  Tom Tromey  <tromey@adacore.com>

* python/python-internal.h (gdb_py_long_from_longest): Remove
defines.
* python/py-value.c (valpy_long): Use gdb_py_object_from_longest.
* python/py-type.c (convert_field, typy_get_sizeof): Use
gdb_py_object_from_longest.
* python/py-record-btrace.c (btpy_list_index): Use
gdb_py_object_from_longest.
gdb/ChangeLog
gdb/python/py-record-btrace.c
gdb/python/py-type.c
gdb/python/py-value.c
gdb/python/python-internal.h