diff options
author | Dimitar Dimitrov <dimitar@dinux.eu> | 2023-12-08 20:39:10 +0200 |
---|---|---|
committer | Dimitar Dimitrov <dimitar@dinux.eu> | 2023-12-28 09:09:13 +0200 |
commit | fcd5cdd5aeecf7eae91a402755c260bb64a0fe0f (patch) | |
tree | e5a61334c906df9657c03e6b391a599af65001f0 /include | |
parent | 73d931e560059a87d76f528fafbb4270a98746bc (diff) | |
download | fsf-binutils-gdb-fcd5cdd5aeecf7eae91a402755c260bb64a0fe0f.zip fsf-binutils-gdb-fcd5cdd5aeecf7eae91a402755c260bb64a0fe0f.tar.gz fsf-binutils-gdb-fcd5cdd5aeecf7eae91a402755c260bb64a0fe0f.tar.bz2 |
sim: pru: Fix emulation of carry bit
The PRU architecture documentation [1] was used for the initial GNU
simulator implementation. But recently [2] TI confirmed the carry
behaviour was wrongly documented. In reality, the PRU carry behaves
like the carry in ARM processors.
This patch fixes simulator to align with latest recommendations from TI.
The new carry.s test was also validated to pass on real hardware -
a BeaglePlay board [3]. That test is a bit long because TI still
has not released official updates for the PRU documents. And I wanted
to ensure simulator handles all edge cases exactly as the real hardware
does.
[1] https://www.ti.com/lit/pdf/spruij2
[2] https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1244359/sk-am64b-am64x-pru-assembler-how-works-this-bloody-carry
[3] https://www.beagleboard.org/boards/beagleplay
Signed-off-by: Dimitar Dimitrov <dimitar@dinux.eu>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions