-
Notifications
You must be signed in to change notification settings - Fork 438
Update jerry submodule #1737
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
Update jerry submodule #1737
Conversation
| static const jerry_char_t *magic_string_items[] = { | ||
| #define MAGICSTR_EX_DEF(NAME, STRING) \ | ||
| (const jerry_char_ptr_t) jerry_magic_string_ex_##NAME, | ||
| (const jerry_char_t *)jerry_magic_string_ex_##NAME, |
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.
Space is missing after the closing bracket.
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.
Actually IoT.js style must be applied here (not JerryScript style), so the space is not needed.
tools/travis_script.py
Outdated
| if buildtype == 'release': | ||
| set_release_config_tizenrt() | ||
| # Fixme: EXTRA_LIBPATHS and EXTRA_LIB can be deleted | ||
| # when TizenRT uses jerry-ext |
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.
Use uppercase letters for fixme, and a dot is missing from the end of the sentence.
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.
Thanks, i missed that. Updated the PR accordingly.
| '--profile=test/profiles/tizenrt.profile', | ||
| 'EXTRA_LIBPATHS=-L' + DOCKER_IOTJS_PATH + | ||
| '/build/arm-tizenrt/' + buildtype + '/lib/', | ||
| 'EXTRA_LIBS=-ljerry-ext']) |
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.
Do you really need to provide the -L / -l option flags in the EXTRA_LIBPATHS and EXTRA_LIBS values?
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.
No need to answer, I see that you need to give it, but I was surprised at first.
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.
.
hs0225
left a comment
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.
LGTM
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.
@Yuyupo Thank you for the contribution!
To All: For debugger, should we take all extensions which could be duplicated with the one in IoT.js? Do we have any alternative? It seems almost harmless but different from the strategy I've understood so far. There was a consensus not to force use of jerry-extension in jerry community so it was separated as the lib. However, debugger seems a different kind.
|
@daeyeon usually the linker deals with the unused functions/features. @Yuyupo, @robertsipka, is this patch cause significant binary gain in any platform? IMHO the main goal of the |
|
Yes, the design goal of jerry-ext is that the extensions are not depend on each other. So the linker can cut the unused parts. However this would be good to check in practice. I agree to check the binary size change. |
|
After the libjerry update, the binary sizes with target and test specific profile builds - that contain all the modules that the tests require - are the following:
With the latest commit on IoT.js (40ee244) are the following:
Conclusion: The binary sizes will be decreased after this patch on these devices. Updated: I noticed that this patch is not rebased with master. The previous commit is 354f28d on the PR, so there may be a difference in the comparison.
|
|
Nice! Thank you for the measurement. |
|
The size will be more decreased if we can take only debugger from the extensions. I'm fine that jerry-ext contains all the non-standard features. However, the more non-standard features merged in future will increase the size of jerry-ext, and that will affect the size of IoT.js. I think that we need to suggest a way in jerryscript to selectively use the features we want. (Currently only debugger) |
|
@Yuyupo jerryscript-project/jerryscript#2507 is merged. Could you update the jerry hash? |
|
@LaszloLango Updated jerry to the latest. |
|
@daeyeon We can open an issue in JerryScript to make the extensions configurable. It would be a good improvement in the engine. It might reduce the compile time too. |
|
@LaszloLango Thank you for the opinion. @Yuyupo I can't guess how much this update is urgent. Could you let me know whether waiting for the configuration is fine to you? |
|
@daeyeon the update is needed for the VS Code Extension, because of the debugger related changes. |
daeyeon
left a comment
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.
LGTM
LaszloLango
left a comment
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.
@Yuyupo Please investigate the Travis failures.
IoT.js-DCO-1.0-Signed-off-by: Daniella Barsony bella@inf.u-szeged.hu
LaszloLango
left a comment
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.
Is the JerryScript hash correct? It looks quite old to me.
Never mind. GitHub tricked me. The JerryScript hash is good. Sorry for the noise.
LaszloLango
left a comment
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.
LGTM
IoT.js-DCO-1.0-Signed-off-by: Daniella Barsony bella@inf.u-szeged.hu