Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add AArch64 support for singlepass. #713

Merged
merged 131 commits into from
Nov 22, 2019
Merged

Add AArch64 support for singlepass. #713

merged 131 commits into from
Nov 22, 2019

Conversation

losfair
Copy link
Contributor

@losfair losfair commented Aug 22, 2019

This PR includes:

  • Support for AArch64 (ARM64) in Singlepass backend. Implemented with a combination of x86_64 instruction translation and native code generation.
  • State tracing and backtraces on AArch64/Singlepass. (Tiering is not implemented for this pair because there's no other backend supporting AArch64 yet)
  • Debugging tools: BlockTrace middleware, and support for reading states of previous WebAssembly stack frames from middlewares.

@losfair losfair force-pushed the feature/singlepass-aarch64 branch from 285d7e9 to e6c6705 Compare September 6, 2019 17:31
@losfair losfair force-pushed the feature/singlepass-aarch64 branch from e6c6705 to 4210715 Compare September 6, 2019 17:32
@losfair losfair force-pushed the feature/singlepass-aarch64 branch from 9ab3da3 to b57aba4 Compare September 17, 2019 18:14
@losfair
Copy link
Contributor Author

losfair commented Nov 21, 2019

bors try

bors bot added a commit that referenced this pull request Nov 21, 2019
@bors
Copy link
Contributor

bors bot commented Nov 22, 2019

try

Build failed

@losfair
Copy link
Contributor Author

losfair commented Nov 22, 2019

bors try

bors bot added a commit that referenced this pull request Nov 22, 2019
@bors
Copy link
Contributor

bors bot commented Nov 22, 2019

try

Build succeeded

@losfair
Copy link
Contributor Author

losfair commented Nov 22, 2019

bors try

bors bot added a commit that referenced this pull request Nov 22, 2019
@bors
Copy link
Contributor

bors bot commented Nov 22, 2019

try

Build succeeded

@syrusakbary
Copy link
Member

bors r+

bors bot added a commit that referenced this pull request Nov 22, 2019
713: Add AArch64 support for singlepass. r=syrusakbary a=losfair

This PR includes:

- Support for AArch64 (ARM64) in Singlepass backend. Implemented with a combination of x86_64 instruction translation and native code generation.
- State tracing and backtraces on AArch64/Singlepass. (Tiering is not implemented for this pair because there's no other backend supporting AArch64 yet)
- Debugging tools: `BlockTrace` middleware, and support for reading states of previous WebAssembly stack frames from middlewares.

Co-authored-by: losfair <[email protected]>
@wasmerio wasmerio deleted a comment from bors bot Nov 22, 2019
@bors
Copy link
Contributor

bors bot commented Nov 22, 2019

Build succeeded

@bors bors bot merged commit 183dd32 into master Nov 22, 2019
@bors bors bot deleted the feature/singlepass-aarch64 branch November 22, 2019 19:00
Copy link
Contributor

@MarkMcCaskey MarkMcCaskey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks pretty good to me! Though a PR this long is very hard to review -- I ended up skipping most of the code generation and translation changes 🤷‍♂ ; it'd be nice if changes like this could be merged in with 10-20 PRs of reasonable size

lib/runtime-core/src/backend.rs Show resolved Hide resolved
lib/runtime-core/src/backend.rs Show resolved Hide resolved
lib/runtime-core/src/backend.rs Show resolved Hide resolved
pub fn setjmp(env: *mut c_void) -> i32;
/// libc longjmp
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We depend on libc in runtime-core; is there a reason we aren't using the libc version?

const TRAP_STACK_SIZE: usize = 1048576; // 1MB

const SETJMP_BUFFER_LEN: usize = 27;
const SETJMP_BUFFER_LEN: usize = 128;
type SetJmpBuffer = [i32; SETJMP_BUFFER_LEN];
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

repinging on this


FaultInfo {
faulting_addr: si_addr as usize as _,
ip: gregs[REG_RIP as usize] as _,
ip: std::mem::transmute::<&mut i64, &'static Cell<usize>>(&mut gregs[REG_RIP as usize]),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this can probably cause undefined behavior but it's pretty subtle. The fact that a normal type in Rust exists that is being accessed with Cell or UnsafeCell is unsound. Cell by way of UnsafeCell is the only way to have aliased mutability in Rust without undefined behavior. This code allows aliased mutability where one side may be a Rust type without Cell or UnsafeCell. I believe that is undefined behavior.

lib/runtime-core/src/state.rs Show resolved Hide resolved
lib/runtime-core/src/state.rs Show resolved Hide resolved
&mut self.machine,
tmp_in,
-1.0,
18446744073709551616.0,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⛳️
u64::max_value() as f64 (if this is the same, then I think it's more readable)

@@ -397,7 +403,7 @@ fn execute_wasm(options: &Run) -> Result<(), String> {
.map_err(|e| format!("Can't convert from wast to wasm: {:?}", e))?;
}

let compiler: Box<dyn Compiler> = match get_compiler_by_backend(options.backend) {
let compiler: Box<dyn Compiler> = match get_compiler_by_backend(options.backend, options) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

repinging on this

bors bot added a commit that referenced this pull request Dec 17, 2019
1068: Various cleanups for the singlepass backend on AArch64. r=losfair a=losfair

ref: #713

Co-authored-by: losfair <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants