diff options
| author | Craig Topper <craig.topper@intel.com> | 2019-05-13 21:01:24 +0000 |
|---|---|---|
| committer | Craig Topper <craig.topper@intel.com> | 2019-05-13 21:01:24 +0000 |
| commit | 5f999c2beaf0a4fbfb4d14d16279f661b29a7e7a (patch) | |
| tree | a0be87ecba9ed2d7dd7ae71279d5fc60cdd0d2fb /lldb/packages/Python/lldbsuite/test/python_api/thread/main.cpp | |
| parent | 56baade10dcf43855faf577554e1810873793da5 (diff) | |
| download | bcm5719-llvm-5f999c2beaf0a4fbfb4d14d16279f661b29a7e7a.tar.gz bcm5719-llvm-5f999c2beaf0a4fbfb4d14d16279f661b29a7e7a.zip | |
[X86] Various type corrections to the code that creates LOCK_OR32mi8/OR32mi8Locked to the stack for idempotent atomic rmw and atomic fence.
These are updates to match how isel table would emit a LOCK_OR32mi8 node.
-Use i32 for the immediate zero even though only 8 bits are encoded.
-Use i16 for segment register.
-Use LOCK_OR32mi8 for idempotent atomic operations in 32-bit mode to match
64-bit mode. I'm not sure why OR32mi8Locked and LOCK_OR32mi8 both exist. The
only difference seems to be that OR32mi8Locked is marked as UnmodeledSideEffects=1.
-Emit an extra i32 result for the flags output.
I don't know if the types here really matter just noticed it was inconsistent
with normal behavior.
llvm-svn: 360619
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/thread/main.cpp')
0 files changed, 0 insertions, 0 deletions
