diff options
author | Simon Marchi <simon.marchi@polymtl.ca> | 2023-03-06 16:46:50 -0500 |
---|---|---|
committer | Simon Marchi <simon.marchi@polymtl.ca> | 2023-03-07 17:45:58 -0500 |
commit | 365aee2bdf90ac99fd749964e18e0c58d7a22383 (patch) | |
tree | 9aaa03f155c922fa785c0c51f7a2f700a580153d /binutils/strings.c | |
parent | 21f6be77b97e1d606881966fd4e407fde459a639 (diff) | |
download | binutils-365aee2bdf90ac99fd749964e18e0c58d7a22383.zip binutils-365aee2bdf90ac99fd749964e18e0c58d7a22383.tar.gz binutils-365aee2bdf90ac99fd749964e18e0c58d7a22383.tar.bz2 |
gdb/amdgpu: provide dummy implementation of gdbarch_return_value_as_value
The AMD GPU support has been merged shortly after commit 4e1d2f5814b2
("Add new overload of gdbarch_return_value"), which made it mandatory
for architectures to provide either a return_value or
return_value_as_value implementation. Because of my failure to test
properly after rebasing and before pushing, we get this with the current
master:
$ gdb ./gdb -nx --data-directory=data-directory -q -ex "set arch amdgcn:gfx1010" -batch
/home/simark/src/binutils-gdb/gdb/gdbarch.c:517: internal-error: verify_gdbarch: the following are invalid ...
return_value_as_value
I started trying to change GDB to not force architectures to provide a
return_value or return_value_as_value implementation, but Andrew pointed
out that any serious port will have an implementation one day or
another, and it's easy to add a dummy implementation in the mean time.
So it's better to not complicate the core of GDB to know how to deal
with this.
There is an implementation of return_value in the downstream ROCgdb port
(which we'll need to convert to the new return_value_as_value), which
we'll contribute soon-ish. In the mean time, add a dummy implementation
of return_value_as_value to avoid the failed assertion.
Change-Id: I26edf441b511170aa64068fd248ab6201158bb63
Reviewed-By: Lancelot SIX <lancelot.six@amd.com>
Diffstat (limited to 'binutils/strings.c')
0 files changed, 0 insertions, 0 deletions