Skip to content
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

ChakraFull/ChakraCore Intl.js bytecode parity #1520

Merged
merged 1 commit into from
Sep 3, 2016

Conversation

tcare
Copy link
Contributor

@tcare tcare commented Aug 31, 2016

This is a precursor to bytecode verification unit tests, which requires ChakraFull to produce the same library bytecode as ChakraCore for Intl.js.

  • Removed an implicit fscrNoAsmJs parser flag in ScriptContext when entering from JSRT. We don't need this flag on the initial entry, so it can be removed from the JSRT entrypoint for library bytecode generation.
  • Zero out bytecode version when generating library bytecode.

@tcare
Copy link
Contributor Author

tcare commented Aug 31, 2016

@curtisman @MikeHolman please review

@@ -418,33 +419,57 @@ class ByteCodeBufferBuilder
}

// library alaways use the release versioning scheme
Copy link
Contributor

Choose a reason for hiding this comment

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

Update comment

@dilijev
Copy link
Contributor

dilijev commented Aug 31, 2016

Please also regen Intl.js.nojit.bc.32b.h (you only regen'd Intl.js.nojit.bc.64b.h for NoJIT)

Also just to be sure everything is good, when you're ready, please run the NoJIT tests: https://github.com/Microsoft/ChakraCore/wiki/Jenkins-Build-Triggers#disablejit-builds

@dilijev
Copy link
Contributor

dilijev commented Aug 31, 2016

LGTM

This is a precursor to bytecode verification unit tests, which requires ChakraFull to produce the same library bytecode as ChakraCore for Intl.js.
- Removed an implicit fscrNoAsmJs parser flag in ScriptContext when entering from JSRT. We don't need this flag on the initial entry, so it can be removed from the JSRT entrypoint for library bytecode generation.
- Zero out bytecode version when generating library bytecode.
@tcare
Copy link
Contributor Author

tcare commented Aug 31, 2016

@dotnet-bot test nojit tests please

@tcare
Copy link
Contributor Author

tcare commented Sep 2, 2016

Ping...

I couldn't repro the disablejit problems, trying again.

@dotnet-bot test nojit tests please

@dilijev
Copy link
Contributor

dilijev commented Sep 2, 2016

@tcare looks good now. Not sure what happened before...

@@ -1700,7 +1700,7 @@ if (!sourceList)

if((loadScriptFlag & LoadScriptFlag_isByteCodeBufferForLibrary) == LoadScriptFlag_isByteCodeBufferForLibrary)
{
grfscr |= (fscrNoAsmJs | fscrNoPreJit);
Copy link
Contributor

@abchatra abchatra Sep 3, 2016

Choose a reason for hiding this comment

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

Why is this change required? Rest of the changes changes look good.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

grfscr gets encoded into library bytecode as part of function body. We don't set it in JsHost, so we don't need to set it in ch either (checked with @MikeHolman)

@abchatra
Copy link
Contributor

abchatra commented Sep 3, 2016

:shipit:

@chakrabot chakrabot merged commit 9d7d5a2 into chakra-core:master Sep 3, 2016
chakrabot pushed a commit that referenced this pull request Sep 3, 2016
Merge pull request #1520 from tcare:bcser

This is a precursor to bytecode verification unit tests, which requires ChakraFull to produce the same library bytecode as ChakraCore for Intl.js.
- Removed an implicit fscrNoAsmJs parser flag in ScriptContext when entering from JSRT. We don't need this flag on the initial entry, so it can be removed from the JSRT entrypoint for library bytecode generation.
- Zero out bytecode version when generating library bytecode.
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.

None yet

5 participants