diff options
| author | Tom Tromey <tromey@adacore.com> | 2023-09-20 09:16:19 -0600 |
|---|---|---|
| committer | Tom Tromey <tromey@adacore.com> | 2023-10-30 07:45:39 -0600 |
| commit | a0bfd1bfa6e7ecdf67bbf11defeb821d9c63e8ef (patch) | |
| tree | 8351e56453dcaabd59d2c6f100fd8d3167b0ad72 /gdb/regcache-dump.c | |
| parent | b4b9074dc0dfab4fb00562b359315d78b09a1564 (diff) | |
| download | gdb-a0bfd1bfa6e7ecdf67bbf11defeb821d9c63e8ef.zip gdb-a0bfd1bfa6e7ecdf67bbf11defeb821d9c63e8ef.tar.gz gdb-a0bfd1bfa6e7ecdf67bbf11defeb821d9c63e8ef.tar.bz2 | |
Fix "finish" for vector types on ARM
On a big-endian ARM system, "finish" printed the wrong value when
finishing from a function that returned a vector type. Similarly,
calls to a function also resulted in the wrong value being passed. I
think both the read- and write-functions here should ignore the
endian-ness.
I tested this using the AdaCore internal test suite; the test case
that caught this is identical to gdb.base/gnu_vector.exp.
Approved-By: Luis Machado <luis.machado@arm.com>
Diffstat (limited to 'gdb/regcache-dump.c')
0 files changed, 0 insertions, 0 deletions