This repository has been archived by the owner on Oct 15, 2020. It is now read-only.
chakrashim: Improve AddLocal and Object::GetPropertyAttributes #101
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist
make -j4 test
(UNIX), orvcbuild test nosign
(Windows) passesAffected core subsystem(s)
chakrashim
Description of change
HandleScope
was simulated in chakrashim by saving referencesin
JavascriptArray
which involved callingJsSetIndexedProperty
API. Although this API is not slow, but there is an overhead of
calling JSRT APIs. It regress performance if
AddLocal
is calledoften. To avoid that, converted the function in javascript which
would call
array.push
of bulk references we recorded so far.Also, I converted
Object::GetPropertyAttributes
to javascriptfunction which should save 6 JSRT calls. I have also added
CHAKRA-TODO
comments for functions that should be easilyconverted to javascript functions.