Skip to content

Conversation

@galpeter
Copy link
Contributor

Based on: #1933

Original author IoT.js-DCO-1.0-Signed-off-by: bence gabor kis [email protected]

message(STATUS "JERRY_MEM_STATS ${FEATURE_MEM_STATS}")
message(STATUS "JERRY_PROFILE ${FEATURE_PROFILE}")
message(STATUS "JERRY_DEBUGGER ${JERRY_DEBUGGER}")
message(STATUS "JERRY_HEAP_SIZE_KB ${JERRY_GLOBAL_HEAP_SIZE}")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this intentionally inconsistent? JERRY_HEAP_SIZE_KB vs JERRY_GLOBAL_HEAP_SIZE

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At the moment I did not want to break the defines/options provided by IoT.js, but I think the name(s) should be normalized in a later change.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm, what I mean is that the name that is printed is not the actual name of the variable that's printed. Shouldn't this be message(STATUS "JERRY_GLOBAL_HEAP_SIZE ${JERRY_GLOBAL_HEAP_SIZE}")?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ahh sorry (was confused by the macro names), true . The original one was also misnamed, but it makes sense to use it the way you mentioned.

tools/build.py Outdated
help='Enable JerryScript heap statistics')
jerry_group.add_argument('--jerry-profile',
metavar='FILE', action='store', default='es5.1',
metavar='FILE', action='store', default='es.next',
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Open question: shall the bump to JerryScript 2.3 also include a bump in the supported ES version?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ohh. I've missed this. I've just wanted to change the comment below. Will update this asap to keep it at es5.1 for now.

@galpeter galpeter force-pushed the jerry_update_v2.3 branch from 78c58b8 to 74bb546 Compare July 30, 2020 13:53
Based on: jerryscript-project#1933

Original author IoT.js-DCO-1.0-Signed-off-by: bence gabor kis [email protected]

IoT.js-DCO-1.0-Signed-off-by: Peter Gal [email protected]
@galpeter galpeter force-pushed the jerry_update_v2.3 branch from 74bb546 to 7d18258 Compare July 30, 2020 14:17
@galpeter
Copy link
Contributor Author

@akosthekiss thanks for the input I've updated the PR.

Copy link
Member

@akosthekiss akosthekiss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

@zherczeg zherczeg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@zherczeg zherczeg merged commit e4e130e into jerryscript-project:master Aug 3, 2020
@rzr
Copy link
Contributor

rzr commented Dec 15, 2020

For the record this change fixes this vulnerability:

https://nvd.nist.gov/vuln/detail/CVE-2020-13649

jerryscript-project/jerryscript#3793

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants