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

atong k22 #1

Open
wants to merge 714 commits into
base: master
Choose a base branch
from
Open

atong k22 #1

wants to merge 714 commits into from

Conversation

atongkuze
Copy link
Owner

No description provided.

akroshg and others added 30 commits May 14, 2020 14:28
Without this we had problem when we are producing returns from the global function when
they are marked as fscrReturnExpression, like in eval case
Fixed this in MustProduceValue function to skip that statement.
Fixes OS : 23989602
* Tidy up some Boolean and Math tests

* Remove unnecessary Conversion test baslines

* Remove more baselines

* Prohibit tests with blank outputs
* Combined module Url and Specifier properties

* Internalise Root Module Detection
Refactor await and yield implementation and enable async iteration

See #6312

Co-authored-by: Kevin Smith <[email protected]>
Merge pull request #6464 from rajeshpeter:servicing/2006

CVE-2020-1219]
Js::PathTypeHandlerBase::SetPrototype should protect against the case where the instance's type is changed as a side-effect of calling newPrototype->GetInternalProperty. Intl.js should not refer directly to the global Intl property, as this may have been modified by the user in such a way that Intl initialization has side-effects. Created an Intl property on the interface object whose value is the built-in Intl object and refer to that in Intl.js instead.

[CVE-2020-1073]
Non-optimized StFld that may change the object's type may be undetected in the loop prepass, resulting in bad AdjustObjType downstream. If the dead store pass detects a final type that's live across a non-optimized StFld, mark the StFld to use a helper that will return true if the object's type is changed, and bail out if the helper returns true. Also ensures there is no type transition live across InitClassMember.
…for 2020.06B

Merge pull request #6464 from rajeshpeter:servicing/2006

CVE-2020-1219]
Js::PathTypeHandlerBase::SetPrototype should protect against the case where the instance's type is changed as a side-effect of calling newPrototype->GetInternalProperty. Intl.js should not refer directly to the global Intl property, as this may have been modified by the user in such a way that Intl initialization has side-effects. Created an Intl property on the interface object whose value is the built-in Intl object and refer to that in Intl.js instead.

[CVE-2020-1073]
Non-optimized StFld that may change the object's type may be undetected in the loop prepass, resulting in bad AdjustObjType downstream. If the dead store pass detects a final type that's live across a non-optimized StFld, mark the StFld to use a helper that will return true if the object's type is changed, and bail out if the helper returns true. Also ensures there is no type transition live across InitClassMember.
Merge pull request #6484 from pleath:timezone-1.11

In some tests, convert Date objects to date strings before displaying them to eliminate timezone sensitivity. In other tests, prevent Microbuild from running the tests to eliminate noise due to timezone.
…in UT's

Merge pull request #6484 from pleath:timezone-1.11

In some tests, convert Date objects to date strings before displaying them to eliminate timezone sensitivity. In other tests, prevent Microbuild from running the tests to eliminate noise due to timezone.
Object.prototype.hasOwnProperty takes undefined when no arg passed in
Remove space from the list separator.

Closes #6361
Rebuild .wasm files in wasm.simd directory using wabt 1.0.20, updating
opcoded accordingly.

Wabt GH: WebAssembly/wabt@830d32a

Removed instructions taken out of the proposal:

- i8x16.mul
- i64x2 truncates
- f64x2 converts
- i64x2.any_true
- i64x2.all_true

Instruction names and text format changes:

- Format literal in v128.const
- `saturate` -> `sat` in names
Order entries by opcode. Mark gaps in numbering with newlines.
Instructions removed from the spec, tests are already updated.
Match `v128.const` text format for tests working with i8x16 and i16x8.
The resulting binary is identical to the `i32x4` constants used
currently.
rhuanjl and others added 30 commits March 22, 2023 08:47
- small changes e.g. alternatives for windows intrinsics
- build file updates
- update DateTimeFormat.js which required ICU_Version<72
- update ICU path for native tests (different on Apple Silicon)
- use find_package for Python
- Build and test Debug, Test and Release Builds
- Cirrus CI supports Apple Silicon
- Not intended to replace Azure for other builds due to usage limits
* Prevent defining `_GUARD_CHECK_ICALL` twice
Newer versions of MVC define _GUARD_CHECK_ICALL after CC defines it
* Throw `ERRBadAwait` instead of `ERRnoSemic` if applicable
Provide a workaround for Clang deleting a check for `this==Empty()`,
where `Empty()` returns null.

Fixes #6847
MSVC neither supports the attribute we've used, nor deletes the check.
Report failing command when regenerating bytecode in addition to the
error.
The file uses va_arg etc, so it should #include <stdarg.h>
Add new copyright notice to pal/src/safecrt/output.inl
Output the the line that failed the check in addition to what has been
found at the top of the file.
Upload `bin` directory to azure artefacts
Set up a cached CMake variable to enable Clang sanitizer.
* Disable JitES6Generators

* Jit Generator and async func LoopBodies

* Update Tests cases for Generator Jit
* Check for errored module before getting Namespace

* Check for missing fetchImportedModuleFromScriptCallback
Add issue templates (forms) to:

- guide authors during issue creation and
- automatically assign labels
Avoid using MSVC-internal `_STRINGIZE`
JsDisableRuntimeExecution currently does not function on AppleSilicon.

This is because of an incorrect ifdef, JsDisableRuntimeExecution works by overriding CC's stack size tracking so that CC mistakenly thinks there is no stack space left and hence stops executing JS; in order to do this StackLimitForScriptInterrupt needs to be an appropriately large number for the architecture, currently it's being set to the same size on AppleSilicon that was used for x86 which is obviously not high enough, change the ifdef so all 64bit architectures (i.e. x64 and AppleSilicon) get the larger figure.

Bug reported by @fatcerberus fix also tested offline by @fatcerberus

Currently most of our native API tests only run on windows hence do not detect this; we should look at enabling them on macOS/Linux as a future todo.
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.