-
Notifications
You must be signed in to change notification settings - Fork 14.3k
WebAssembly: Move runtime libcall setting out of TargetLowering #142624
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
This file was deleted.
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -531,6 +531,11 @@ void RuntimeLibcallsInfo::initLibcalls(const Triple &TT) { | |
setLibcallName(RTLIB::MULO_I64, nullptr); | ||
} | ||
setLibcallName(RTLIB::MULO_I128, nullptr); | ||
} else { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. IIRC to preserve existing behavior and because these libcalls were listed in RuntimeLibcallSignatureTable. I don't think wasm is typically used with libgcc? Is that supported? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. AFAIK there are no uses of libgcc with wasm. |
||
// Define the emscripten name for return address helper. | ||
// TODO: when implementing other Wasm backends, make this generic or only do | ||
// this on emscripten depending on what they end up doing. | ||
setLibcallName(RTLIB::RETURN_ADDRESS, "emscripten_return_address"); | ||
} | ||
|
||
if (TT.isSystemZ() && TT.isOSzOS()) { | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be
if (TT.isOSEmscripten())
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suspect this predates when we had an emscripten triple, and it should probably be behind
isOSEmscripten()
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not looking to change behavior here, this should be done separately