diff options
author | Tom Tromey <tromey@adacore.com> | 2022-09-07 08:39:52 -0600 |
---|---|---|
committer | Tom Tromey <tromey@adacore.com> | 2023-01-03 08:45:00 -0700 |
commit | 4e1d2f5814b29048d1dd1cea2cb50570e6c8f1f8 (patch) | |
tree | c5b684d3cad8e726247e58566b9d293ece12b756 /gdb/ppc-linux-tdep.c | |
parent | 862ebb27bbe30768356776a10827dd1c0824d405 (diff) | |
download | binutils-4e1d2f5814b29048d1dd1cea2cb50570e6c8f1f8.zip binutils-4e1d2f5814b29048d1dd1cea2cb50570e6c8f1f8.tar.gz binutils-4e1d2f5814b29048d1dd1cea2cb50570e6c8f1f8.tar.bz2 |
Add new overload of gdbarch_return_value
The gdbarch "return_value" can't correctly handle variably-sized
types. The problem here is that the TYPE_LENGTH of such a type is 0,
until the type is resolved, which requires reading memory. However,
gdbarch_return_value only accepts a buffer as an out parameter.
Fixing this requires letting the implementation of the gdbarch method
resolve the type and return a value -- that is, both the contents and
the new type.
After an attempt at this, I realized I wouldn't be able to correctly
update all implementations (there are ~80) of this method. So,
instead, this patch adds a new method that falls back to the current
method, and it updates gdb to only call the new method. This way it's
possible to incrementally convert the architectures that I am able to
test.
Diffstat (limited to 'gdb/ppc-linux-tdep.c')
0 files changed, 0 insertions, 0 deletions