WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
NEW
159775
WebAssembly: support the newer spec
https://bugs.webkit.org/show_bug.cgi?id=159775
Summary
WebAssembly: support the newer spec
Keith Miller
Reported
2016-07-14 11:47:09 PDT
We should totes do this.
Attachments
Patch
(31.91 KB, patch)
2016-10-20 13:39 PDT
,
Keith Miller
no flags
Details
Formatted Diff
Diff
Show Obsolete
(1)
View All
Add attachment
proposed patch, testcase, etc.
Keith Miller
Comment 1
2016-10-20 13:39:04 PDT
Created
attachment 292244
[details]
Patch
Keith Miller
Comment 2
2016-10-20 13:42:07 PDT
Crap, I uploaded this to the wrong bug...
Geoffrey Garen
Comment 3
2016-10-20 13:54:56 PDT
Comment on
attachment 292244
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=292244&action=review
> Source/JavaScriptCore/ChangeLog:12 > + address we need to call to. For each callsite in the compiling function WASM remembers what
remembers what => remembers
> Source/JavaScriptCore/ChangeLog:14 > + each functions callsites are linked to the appropriate entrypoint.
each callsite is linked to the appropriate entrypoint
> Source/JavaScriptCore/wasm/WASMB3IRGenerator.cpp:220 > + Vector<UnlinkedLocationInfo>& m_unlinkedCalls;
UnlinkedLocationInfo holds a single CodeLocationCall. What's the "list of of callsites"?
> Source/JavaScriptCore/wasm/WASMB3IRGenerator.cpp:588 > + *callSiteLinkLocation = { linkBuffer.locationOf(call), functionIndex };
If m_unlinkedCalls grows enough before this patchpoint generator runs, callSiteLinkLocation becomes a stale pointer. I think you want an index instead of a pointer.
> Source/JavaScriptCore/wasm/WASMFormat.h:131 > +struct UnlinkedLocationInfo {
Can we call this UnlinkedCall or UnlinkedWASMCall or UnlinkedCallInfo? 'Location' is pretty vague.
JF Bastien
Comment 4
2017-01-03 20:39:10 PST
***
Bug 161728
has been marked as a duplicate of this bug. ***
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