WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
178690
WebAssembly: topEntryFrame on Wasm::Instance
https://bugs.webkit.org/show_bug.cgi?id=178690
Summary
WebAssembly: topEntryFrame on Wasm::Instance
JF Bastien
Reported
2017-10-23 16:37:09 PDT
topEntryFrame is usually on VM, but for a no-VM WebAssembly we need to hold topEntryFrame elsewhere, and generated code cannot hard-code where topEntryFrame live. Do this at creation time of Wasm::Instance, and then generated code will just load from wherever Wasm::Instance was told topEntryFrame is. In a JavaScript embedding this is still from VM, so all of the unwinding machinery stays the same.
Attachments
patch
(25.22 KB, patch)
2017-10-23 16:46 PDT
,
JF Bastien
saam
: review+
Details
Formatted Diff
Diff
patch
(25.16 KB, patch)
2017-10-23 16:54 PDT
,
JF Bastien
no flags
Details
Formatted Diff
Diff
Show Obsolete
(1)
View All
Add attachment
proposed patch, testcase, etc.
JF Bastien
Comment 1
2017-10-23 16:46:47 PDT
Created
attachment 324611
[details]
patch
Saam Barati
Comment 2
2017-10-23 16:49:35 PDT
Comment on
attachment 324611
[details]
patch View in context:
https://bugs.webkit.org/attachment.cgi?id=324611&action=review
> Source/JavaScriptCore/wasm/js/JSWebAssemblyInstance.h:137 > + EntryFrame** m_topEntryFramePointer { nullptr };
Why have this in both JSWebAssemblyInstance and WasmInstance?
JF Bastien
Comment 3
2017-10-23 16:51:48 PDT
(In reply to Saam Barati from
comment #2
)
> Comment on
attachment 324611
[details]
> patch > > View in context: >
https://bugs.webkit.org/attachment.cgi?id=324611&action=review
> > > Source/JavaScriptCore/wasm/js/JSWebAssemblyInstance.h:137 > > + EntryFrame** m_topEntryFramePointer { nullptr }; > > Why have this in both JSWebAssemblyInstance and WasmInstance?
JSWebAssemblyInstance copies a bunch of things from Wasm::Instance for now, because the goal I'm driving towards is having Wasm::Context be Wasm::Instance (not JSWebAssemblyInstance), and I want the swap to be as trivial as possible (i.e. change one line to do that swap, then delete all the copies from JSWebAssemblyInstance). If I do it right everything else will be the same.
JF Bastien
Comment 4
2017-10-23 16:54:31 PDT
Created
attachment 324613
[details]
patch
WebKit Commit Bot
Comment 5
2017-10-23 17:29:43 PDT
Comment on
attachment 324613
[details]
patch Clearing flags on attachment: 324613 Committed
r223866
: <
https://trac.webkit.org/changeset/223866
>
WebKit Commit Bot
Comment 6
2017-10-23 17:29:45 PDT
All reviewed patches have been landed. Closing bug.
Keith Miller
Comment 7
2017-10-23 19:01:52 PDT
I think this broke the windows build?
https://build.webkit.org/builders/Apple%20Win%20Release%20%28Build%29/builds/5466/steps/compile-webkit/logs/stdio
WebKit Commit Bot
Comment 8
2017-10-23 19:31:27 PDT
Re-opened since this is blocked by
bug 178699
Keith Miller
Comment 9
2017-10-23 20:20:37 PDT
Committed
r223875
: <
https://trac.webkit.org/changeset/223875
>
JF Bastien
Comment 10
2017-10-23 21:58:33 PDT
(In reply to Keith Miller from
comment #7
)
> I think this broke the windows build? >
https://build.webkit.org/builders/Apple%20Win%20Release%20%28Build%29/builds/
> 5466/steps/compile-webkit/logs/stdio
lolwut?
Radar WebKit Bug Importer
Comment 11
2017-11-15 12:58:18 PST
<
rdar://problem/35568509
>
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug