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.
This commit is contained in:
Tom Tromey
2020-09-15 11:08:56 -06:00
parent 3743107465
commit 4bde49dc81
5 changed files with 15 additions and 9 deletions

View File

@ -556,7 +556,7 @@ btpy_list_index (PyObject *self, PyObject *value)
if (index < 0)
return PyErr_Format (PyExc_ValueError, _("Not in list."));
return gdb_py_long_from_longest (index);
return gdb_py_object_from_longest (index).release ();
}
/* Implementation of BtraceList.count (self, value) -> int. */