diff options
author | Gabe Black <gabeblack@google.com> | 2017-12-12 17:54:58 -0800 |
---|---|---|
committer | Gabe Black <gabeblack@google.com> | 2017-12-13 23:50:53 +0000 |
commit | 36d5e8925526b15d1638ac44380e4ada5af16e08 (patch) | |
tree | ed561a8a5ca4057467d015d1c6366229824e1bbb /src/arch/sparc/pseudo_inst.hh | |
parent | a8f82f545abd27657e19a91dd6b9675a576b116b (diff) | |
download | gem5-36d5e8925526b15d1638ac44380e4ada5af16e08.tar.xz |
x86: Rework how "split" loads/stores are handled.
Explicitly separate the way the data is represented in the underlying
representation from how it's represented in the instruction.
In order to make the ISA parser happy, the Mem operand needs to have
a single, particular type. To handle that with scalar types, we just
used uint64_ts and then worked with values that were smaller than the
maximum we could hold. To work with these new array values, we also
use an underlying uint64_t for each element.
To make accessing the underlying memory system more natural, when we
go to actually read or write values, we translate the access into an
array of the actual, correct underlying type. That way we don't have
non-exact asserts which confuse gcc, or weird endianness conversion
which assumes that the data should be flipped 8 bytes at a time.
Because the functions involved are generally inline, the syntactic
niceness should all boil off, and the final implementation in the
binary should be simple and efficient for the given data types.
Change-Id: I14ce7a2fe0dc2cbaf6ad4a0d19f743c45ee78e26
Reviewed-on: https://gem5-review.googlesource.com/6582
Reviewed-by: Gabe Black <gabeblack@google.com>
Maintainer: Gabe Black <gabeblack@google.com>
Diffstat (limited to 'src/arch/sparc/pseudo_inst.hh')
0 files changed, 0 insertions, 0 deletions