issue_owner_repo listlengths 2 2 | issue_body stringlengths 0 261k ⌀ | issue_title stringlengths 1 925 | issue_comments_url stringlengths 56 81 | issue_comments_count int64 0 2.5k | issue_created_at stringlengths 20 20 | issue_updated_at stringlengths 20 20 | issue_html_url stringlengths 37 62 | issue_github_id int64 387k 2.46B | issue_number int64 1 127k |
|---|---|---|---|---|---|---|---|---|---|
[
"chakra-core",
"ChakraCore"
] | ```
(function() {
"use asm";
m => 0;
})()
```
$ ~/chakracore/BuildLinux/Debug/ch 1case.js
ASSERTION 65750: (/home/skywinlinvm/chakracore/lib/Parser/Parse.cpp, line 5147) Deferring function parsing of a function does not handle lambda syntax
Failure: (!fLambda)
Illegal instruction (core dumped)
$... | Assertion failure: "Deferring function parsing of a function does not handle lambda syntax" with "use asm" and arrow function | https://api.github.com/repos/chakra-core/ChakraCore/issues/2237/comments | 2 | 2016-12-18T04:02:14Z | 2017-05-24T03:18:41Z | https://github.com/chakra-core/ChakraCore/issues/2237 | 196,256,805 | 2,237 |
[
"chakra-core",
"ChakraCore"
] | **Steps to reproduce:**
1. Go to Settings > Time & Language > Region & Language > Additional date, time, & regional settings > Change date, time, or number formats.
2. Choose any format other than "Match Windows display language". In my case format is Russian (Russia), and my display language is English (United Sta... | `NavigatorLanguage.language` property reports format language instead of Windows display language | https://api.github.com/repos/chakra-core/ChakraCore/issues/2235/comments | 2 | 2016-12-17T02:57:59Z | 2016-12-17T03:15:55Z | https://github.com/chakra-core/ChakraCore/issues/2235 | 196,191,946 | 2,235 |
[
"chakra-core",
"ChakraCore"
] | It is often the case that regressions in daily configurations go unnoticed in PRs. I believe we can pick a representative sample of builds from other configurations which will catch issues without significantly bloating the number of checks we run per PR.
The extra checks we add will not be exhaustive because they w... | Add one flavor each of Legacy and DisableJIT builds to PR checks to catch regressions | https://api.github.com/repos/chakra-core/ChakraCore/issues/2229/comments | 2 | 2016-12-16T23:41:53Z | 2017-01-30T22:34:06Z | https://github.com/chakra-core/ChakraCore/issues/2229 | 196,178,206 | 2,229 |
[
"chakra-core",
"ChakraCore"
] | Linux support would allow us to use a wider variety of static and dynamic analysis tools on the WASM code. | WASM: Linux Support | https://api.github.com/repos/chakra-core/ChakraCore/issues/2220/comments | 3 | 2016-12-16T02:20:24Z | 2017-02-23T12:15:29Z | https://github.com/chakra-core/ChakraCore/issues/2220 | 195,966,021 | 2,220 |
[
"chakra-core",
"ChakraCore"
] | In ChakraFull we POGO Test builds (rather than Release builds) because we need performance-optimized Test builds for testing purposes. The pogo_training.ps1 script is used to do the POGO training in ChakraFull as well. In the case of ChakraFull, extra parameters like `-oopjit-` work just fine.
We had not yet noticed... | pogo_training.ps1 using `-oopjit-` flag breaks POGO training for ChakraCore release builds | https://api.github.com/repos/chakra-core/ChakraCore/issues/2213/comments | 3 | 2016-12-15T22:53:22Z | 2016-12-16T01:15:24Z | https://github.com/chakra-core/ChakraCore/issues/2213 | 195,937,903 | 2,213 |
[
"chakra-core",
"ChakraCore"
] | I have an attribute selector stored as a string. I pass it as an argument to `querySelectorAll` as in the code below. An error is thrown. See screenshot.
```
const ITEM = '[data-showflex="container"]',
STATECLASS = 'show';
function showAllItems() {
document.querySelectorAll(ITEM).forEach((item) => item... | JavaScript Bug When Referencing Variable Storing Attribute Selector String | https://api.github.com/repos/chakra-core/ChakraCore/issues/2212/comments | 2 | 2016-12-15T21:05:19Z | 2017-01-06T00:10:40Z | https://github.com/chakra-core/ChakraCore/issues/2212 | 195,915,637 | 2,212 |
[
"chakra-core",
"ChakraCore"
] | After #1990 fixed #2026, another unrelated issue was revealed. It would be helpful to coordinate with @MikeHolman re #1990 to make sure both issues are fixed.
See logs from the errored tests under #1990. Error copied below:
```
19:21:40 D:\j\workspace\daily_dev12_x---c4e76fe7\Lib\Jsrt\ChakraCore.h(215): error C4... | [Legacy] Missing type | https://api.github.com/repos/chakra-core/ChakraCore/issues/2194/comments | 1 | 2016-12-12T22:54:30Z | 2016-12-15T23:08:57Z | https://github.com/chakra-core/ChakraCore/issues/2194 | 195,110,184 | 2,194 |
[
"chakra-core",
"ChakraCore"
] | When reading mutable value for globals `bool isMutable = ReadConst<UINT8>() == 1;`, we have to explicitly check for value 0 or 1 and throw if anything else | WASM - global mutable value | https://api.github.com/repos/chakra-core/ChakraCore/issues/2193/comments | 0 | 2016-12-12T22:15:44Z | 2016-12-20T22:15:38Z | https://github.com/chakra-core/ChakraCore/issues/2193 | 195,101,377 | 2,193 |
[
"chakra-core",
"ChakraCore"
] | This may not be the same Module API as what is currently available, but I figured most users would like a straight forward method to register custom Modules using the current strings api. For the most part the custom modules should automatically get cleaned out by garbage collection, and are straight forward on usage. ... | Simplify C/C++ Module Creation | https://api.github.com/repos/chakra-core/ChakraCore/issues/2186/comments | 4 | 2016-12-12T02:35:54Z | 2018-05-07T22:11:19Z | https://github.com/chakra-core/ChakraCore/issues/2186 | 194,878,685 | 2,186 |
[
"chakra-core",
"ChakraCore"
] | `bin\ch\hostconfigflags.cpp(99): warning C6385: Reading invalid data from 'argv': the readable size is 'argc*8' bytes, but '24' bytes may be read.`
git blame shows this was introduced a few months ago:
```
10cfef1f (Michael Holman 2016-09-02 20:36:55 -0700 99) argv[i - 1] = argv[i];
```
Discovered ... | [x64 release] bin\ch\hostconfigflags.cpp(99): warning C6385: Reading invalid data from 'argv' | https://api.github.com/repos/chakra-core/ChakraCore/issues/2183/comments | 1 | 2016-12-09T23:33:09Z | 2017-12-05T02:22:25Z | https://github.com/chakra-core/ChakraCore/issues/2183 | 194,722,765 | 2,183 |
[
"chakra-core",
"ChakraCore"
] | Are stack overflow exception supposed to throw WebAssembly.RuntimeError if they happen on a webassembly frame? | WASM - StackOverflow error as WebAssembly.RuntimeError | https://api.github.com/repos/chakra-core/ChakraCore/issues/2167/comments | 3 | 2016-12-08T02:08:33Z | 2016-12-20T00:33:05Z | https://github.com/chakra-core/ChakraCore/issues/2167 | 194,228,739 | 2,167 |
[
"chakra-core",
"ChakraCore"
] | Legacy builds are failing with the following error:
D:\j\workspace\daily_dev12_x---55cdd258\lib\Runtime\Library\WebAssemblyTable.cpp(124): error C2070: 'unknown': illegal sizeof operand [D:\j\workspace\daily_dev12_x---55cdd258\lib\Runtime\Library\Chakra.Runtime.Library.vcxproj]
Assigning as per last person to cha... | Legacy builds failing on illegal sizeof | https://api.github.com/repos/chakra-core/ChakraCore/issues/2163/comments | 1 | 2016-12-07T20:33:29Z | 2016-12-09T23:37:06Z | https://github.com/chakra-core/ChakraCore/issues/2163 | 194,161,354 | 2,163 |
[
"chakra-core",
"ChakraCore"
] | As mentioned in https://github.com/Microsoft/ChakraCore/pull/2001#issuecomment-263711770
/cc @jianchun @mrkmarron | Update usage of JsTTDGetSnapTimeTopLevelEventMove in xplat branch | https://api.github.com/repos/chakra-core/ChakraCore/issues/2161/comments | 3 | 2016-12-07T04:01:00Z | 2017-05-17T22:39:24Z | https://github.com/chakra-core/ChakraCore/issues/2161 | 193,952,744 | 2,161 |
[
"chakra-core",
"ChakraCore"
] | Previously it has been noted by some members of the community that [ChakraCore Samples in the Chakra-Samples project](https://github.com/Microsoft/Chakra-Samples/tree/master/ChakraCore%20Samples) have not worked with the current ChakraCore master. These could be temporary regressions but they are not tracked by any aut... | Add tests (here or in Chakra-Samples) to ensure ChakraCore Samples don't break. | https://api.github.com/repos/chakra-core/ChakraCore/issues/2160/comments | 6 | 2016-12-07T03:29:06Z | 2018-03-01T01:37:50Z | https://github.com/chakra-core/ChakraCore/issues/2160 | 193,949,110 | 2,160 |
[
"chakra-core",
"ChakraCore"
] | Due to the difference in argument permissibility for TypedArray constructors now, the baseline for this test no longer matches up with the output generated by running the test. I believe that the new output is correct, but assigning to Ian because he knows this change better. | Fix tests/typedarray/samethread.baseline | https://api.github.com/repos/chakra-core/ChakraCore/issues/2159/comments | 0 | 2016-12-07T03:21:56Z | 2016-12-17T02:40:30Z | https://github.com/chakra-core/ChakraCore/issues/2159 | 193,948,270 | 2,159 |
[
"chakra-core",
"ChakraCore"
] | The compiler we use in ChakraFull doesn't generate the same thing for mul/div with doubles as it does for ch.exe
The instruction set generated is
```asm
fld aLeft
fdiv/fmul aRight
```
The instructions we should use are
```asm
movsd xmm0, aLeft
divsd/mulsd xmm0, aRight
```
After fixing this, need to re-e... | WASM - f64.mul/div interpreter precision on x86 | https://api.github.com/repos/chakra-core/ChakraCore/issues/2145/comments | 0 | 2016-12-06T00:53:18Z | 2016-12-20T00:33:05Z | https://github.com/chakra-core/ChakraCore/issues/2145 | 193,653,964 | 2,145 |
[
"chakra-core",
"ChakraCore"
] | Add a test run with -nonative on wasm spec tests | WASM - Spec tests with nonative | https://api.github.com/repos/chakra-core/ChakraCore/issues/2142/comments | 0 | 2016-12-05T21:10:10Z | 2016-12-20T00:33:05Z | https://github.com/chakra-core/ChakraCore/issues/2142 | 193,610,848 | 2,142 |
[
"chakra-core",
"ChakraCore"
] | When executing JS script on Linux we get an error saying "SyntaxError: Invalid character"
Script|Succeeds|comment
---|---|---
$global.data[1];|false|Seems to fail due to semicolon|
$global.data[1]|true|Succeeds without semicolon|
function foo(){ var a = [true,false]; return a; } |true|
function foo(){ var a = [... | Syntax Error on Ubuntu v. 16 (ChakraCore v. 1.3.1) | https://api.github.com/repos/chakra-core/ChakraCore/issues/2141/comments | 3 | 2016-12-05T15:00:01Z | 2016-12-06T15:24:55Z | https://github.com/chakra-core/ChakraCore/issues/2141 | 193,520,456 | 2,141 |
[
"chakra-core",
"ChakraCore"
] | As a JIT, ChakraCore has its own allocator for executable machine code. This is a feature request to expose this to embedders. | Feature request: Expose ChakraCore machine code allocator via JSRT | https://api.github.com/repos/chakra-core/ChakraCore/issues/2139/comments | 1 | 2016-12-04T01:35:38Z | 2018-02-22T00:19:16Z | https://github.com/chakra-core/ChakraCore/issues/2139 | 193,325,437 | 2,139 |
[
"chakra-core",
"ChakraCore"
] | New xplat CI found that `test/typedarray/samethread.js` fails after #2016 is being merged.
Repro: (on any distro or osx)
- Build [test-build]
- `test/runtests.py -t --include-slow test/typedarray`
Assigning this to @ianwjhalliday as [#2016] PR is the reason. | SlowTest-Fail: typedarray/samethread.js fails after #2016 | https://api.github.com/repos/chakra-core/ChakraCore/issues/2135/comments | 2 | 2016-12-02T00:40:11Z | 2016-12-17T02:00:35Z | https://github.com/chakra-core/ChakraCore/issues/2135 | 193,003,261 | 2,135 |
[
"chakra-core",
"ChakraCore"
] | The C++ compiler in x86 generates fstp instruction for float return values. This instruction changes the bit pattern of signaling float NaN (For example: from 0x7f80f1e2 to 0x7fc0f1e2). This is problematic in Wasm, as it relies on NaN bit patterns. In x86 debug all signaling NaNs will be canonicalized and we see unifor... | Wasm: Inconsistent representation of signalling NaNs in x86 test | https://api.github.com/repos/chakra-core/ChakraCore/issues/2125/comments | 0 | 2016-11-30T17:59:21Z | 2017-08-17T00:49:09Z | https://github.com/chakra-core/ChakraCore/issues/2125 | 192,636,209 | 2,125 |
[
"chakra-core",
"ChakraCore"
] | This character was recategorized from Zs to Cf in Unicode 6.3, and remains categorized as such in Unicode 9.0 (current target version). The current version of ECMAScript requires that only characters classed as Zs in the target version of Unicode be recognized as Whitespace. This change is now reflected in Test262 so m... | [RegExp] Remove U+180E MONGOLIAN VOWEL SEPARATOR from Whitespace classification. | https://api.github.com/repos/chakra-core/ChakraCore/issues/2120/comments | 0 | 2016-11-30T03:35:34Z | 2016-12-07T00:51:24Z | https://github.com/chakra-core/ChakraCore/issues/2120 | 192,467,147 | 2,120 |
[
"chakra-core",
"ChakraCore"
] | The parser for legacy reasons allows parenthesized label names. ECMA262 spec doesn't allow this in the grammar nor in Annex B. Likewise, Chrome and many other JavaScript parsers do not recognize it.
This appears to be an old IE specific behavior, and changing it in Chakra is highly unlikely to break the web. Coul... | Remove parser allowance of parenthesized label names | https://api.github.com/repos/chakra-core/ChakraCore/issues/2119/comments | 0 | 2016-11-30T01:05:25Z | 2017-12-05T02:31:20Z | https://github.com/chakra-core/ChakraCore/issues/2119 | 192,447,405 | 2,119 |
[
"chakra-core",
"ChakraCore"
] | I'm using the master branch + PR #2056, latest of a few moments ago.
The following methods seem to be missing from both 'nix and macOS:
- JsInitializeModuleRecord
- JsSetModuleHostInfo
- JsParseModuleSource
- JsModuleEvaluation
The following tests are passing in windows, but failing on ubuntu/osx CI ... | xplat: Missing ES6 Module functionality in Linux and macOS | https://api.github.com/repos/chakra-core/ChakraCore/issues/2112/comments | 7 | 2016-11-29T19:32:34Z | 2017-01-11T15:38:55Z | https://github.com/chakra-core/ChakraCore/issues/2112 | 192,377,129 | 2,112 |
[
"chakra-core",
"ChakraCore"
] | Exported Functions also have the following data properties: the length property is set to the exported function's signature's arity
the name is set to index as a Number value
Depends on #2452 | WASM - exported function properties (4d) | https://api.github.com/repos/chakra-core/ChakraCore/issues/2101/comments | 0 | 2016-11-28T20:21:10Z | 2017-09-19T22:59:29Z | https://github.com/chakra-core/ChakraCore/issues/2101 | 192,107,401 | 2,101 |
[
"chakra-core",
"ChakraCore"
] | Both the in-solution build in react-native-windows and from the Developer Command Prompt for VS2017 RC, I get this message:
1> "C:\Users\matt.hargett\Source\Repos\rnw-mh\ChakraCore\Build\Chakra.Core.sln" (Core\Bin\ChakraCore target) (1) ->
1> "C:\Users\matt.hargett\Source\Repos\rnw-mh\ChakraCore\Build\.... | neither master nor release/2.0-pre build with VS2017 RC | https://api.github.com/repos/chakra-core/ChakraCore/issues/2096/comments | 4 | 2016-11-27T04:34:07Z | 2017-05-31T18:24:14Z | https://github.com/chakra-core/ChakraCore/issues/2096 | 191,841,870 | 2,096 |
[
"chakra-core",
"ChakraCore"
] | I've executed the following code both with JSRT Legacy (jscript9.dll) and with the release version 1.3.0 of ChakraCore and have received very different results.
In case of version 1.3.0 the code has successfully completed.
In case of JSRT Legacy the code has thrown an exception of type `JavaScriptUsageException` ... | Isolation of Execution Contexts | https://api.github.com/repos/chakra-core/ChakraCore/issues/2092/comments | 4 | 2016-11-24T22:43:21Z | 2017-03-04T02:59:03Z | https://github.com/chakra-core/ChakraCore/issues/2092 | 191,599,124 | 2,092 |
[
"chakra-core",
"ChakraCore"
] | Open the developer console for logs.
Call Object.freeze on an array and set an element outside of the array's bounds.
Expected result: An exception is thrown
Actual result: No exception is thrown
This does not repro when setting elements inside the bounds of the array.
'use strict';
var ar... | Setting an element outside the bounds of a frozen array does not throw an exception | https://api.github.com/repos/chakra-core/ChakraCore/issues/2083/comments | 2 | 2016-11-23T01:46:55Z | 2016-12-17T09:31:47Z | https://github.com/chakra-core/ChakraCore/issues/2083 | 191,170,914 | 2,083 |
[
"chakra-core",
"ChakraCore"
] | Currently, when we handle "var x = new Array()", we allocate space for additional profile information on the array creation site. This allows us to do some optimizations and create native arrays, which are significantly faster in many cases. However, we can't currently do this for "var x = Array()". We had an attempt a... | Create native arrays for bare Array() calls | https://api.github.com/repos/chakra-core/ChakraCore/issues/2082/comments | 4 | 2016-11-22T19:34:25Z | 2019-06-07T19:11:16Z | https://github.com/chakra-core/ChakraCore/issues/2082 | 191,103,154 | 2,082 |
[
"chakra-core",
"ChakraCore"
] | We have compile time problems with Clang 4.0 and keeping this issue in order to track that. | clang 4.0: fix build issues | https://api.github.com/repos/chakra-core/ChakraCore/issues/2080/comments | 1 | 2016-11-22T17:56:43Z | 2017-03-10T08:28:16Z | https://github.com/chakra-core/ChakraCore/issues/2080 | 191,079,940 | 2,080 |
[
"chakra-core",
"ChakraCore"
] | Our libunwind usage is very limited (PAL) and we don't actually expect SEH support on xplat.
| xplat: Remove libunwind dependency | https://api.github.com/repos/chakra-core/ChakraCore/issues/2079/comments | 1 | 2016-11-22T17:55:27Z | 2016-12-14T05:30:37Z | https://github.com/chakra-core/ChakraCore/issues/2079 | 191,079,626 | 2,079 |
[
"chakra-core",
"ChakraCore"
] | For every helper call to throw in jit, we spill the register to save them. This is not necessary as we never come back from the helper | Spilling caller save register on helper call that always throws (3d) | https://api.github.com/repos/chakra-core/ChakraCore/issues/2075/comments | 1 | 2016-11-21T23:30:56Z | 2017-05-18T18:18:26Z | https://github.com/chakra-core/ChakraCore/issues/2075 | 190,866,332 | 2,075 |
[
"chakra-core",
"ChakraCore"
] | We brought back custom `JsUtil::QuickSort` in swb branch to solve the problem that system qsort routine does not update write barrier when array element contains WriteBarrierPtr fields.
We need to fine tune `JsUtil::QuickSort` performance. Current implementation does not work well with already sorted or many equal i... | swb: tune JsUtil::QuickSort implementation | https://api.github.com/repos/chakra-core/ChakraCore/issues/2074/comments | 2 | 2016-11-21T19:49:15Z | 2017-02-23T17:11:33Z | https://github.com/chakra-core/ChakraCore/issues/2074 | 190,817,595 | 2,074 |
[
"chakra-core",
"ChakraCore"
] | I created a object A, and added some member.
JsCreateObject
created external object B, and set prototype with A. C is finalizeCallback.
JsCreateExternalObject, JsSetPrototype
do gc.
JsCollectGarbage
why not call finalizeCallback C?
I tryed to call JsRelease(B, count) too, count is return (uint)-1, but use... | About JsObject's reference and release | https://api.github.com/repos/chakra-core/ChakraCore/issues/2072/comments | 5 | 2016-11-21T15:49:08Z | 2016-11-29T01:31:18Z | https://github.com/chakra-core/ChakraCore/issues/2072 | 190,755,203 | 2,072 |
[
"chakra-core",
"ChakraCore"
] | Some of our `debug` related tests provide fake filenames for scripts.
For example;
```
var x = WScript.LoadScript("function foo(){}", "samethread", "dummyFileName.js");
```
In case the `dummyFileName.js` is not exist on the actual folder, this particular call returns `undefined` back to JS land.
Expected b... | ch: LoadScript with fake script filename fails on xplat | https://api.github.com/repos/chakra-core/ChakraCore/issues/2065/comments | 1 | 2016-11-19T14:18:55Z | 2017-01-11T15:39:26Z | https://github.com/chakra-core/ChakraCore/issues/2065 | 190,498,658 | 2,065 |
[
"chakra-core",
"ChakraCore"
] | Opening this issue to track disabled test cases
`DebuggerCommon/TypedArray.js`
```
* thread #1: tid = 79144, 0x0000555555923a4b ch`Js::Amd64StackFrame::Next() + 11, name = 'ch', stop reason = signal SIGSEGV: invalid address (fault address: 0x9)
frame #0: 0x0000555555923a4b ch`Js::Amd64StackFrame::Next() + 1... | xplat-debugger: DebuggerCommon test fails [JIT] [test] | https://api.github.com/repos/chakra-core/ChakraCore/issues/2064/comments | 0 | 2016-11-19T14:03:18Z | 2018-02-09T23:49:29Z | https://github.com/chakra-core/ChakraCore/issues/2064 | 190,498,020 | 2,064 |
[
"chakra-core",
"ChakraCore"
] | In https://github.com/Microsoft/ChakraCore/commit/57962d5ebc8640a9f86294d602a69bcd0053cd13 I had to disable an optimization to elevate BailOnNoProfile instructions, because we do not have accurate enough data for operand fgPeepTmp properties. Fixing the propagation of these values should allow re-enabling this optimiza... | Fix fgPeepTmp annotation and re-enable related BailOnNoProfile Optimization | https://api.github.com/repos/chakra-core/ChakraCore/issues/2062/comments | 2 | 2016-11-19T03:26:01Z | 2019-06-07T19:11:20Z | https://github.com/chakra-core/ChakraCore/issues/2062 | 190,473,492 | 2,062 |
[
"chakra-core",
"ChakraCore"
] | Building ChakraCore on OSx 10.12.1 from master with latest using
``` bash
./build.sh --icu=/usr/local/opt/icu4c/include -j=4
```
When running ```nm -g libChakraCore.dylib``` on the resulting library, I see the JsTDDxxx symbols exported but not methods such as JsDiagStartDebugging as found on the Windows API.
... | xplat: ChakraDebug API missing from OSx build | https://api.github.com/repos/chakra-core/ChakraCore/issues/2058/comments | 4 | 2016-11-19T00:27:21Z | 2016-12-23T15:45:37Z | https://github.com/chakra-core/ChakraCore/issues/2058 | 190,453,345 | 2,058 |
[
"chakra-core",
"ChakraCore"
] | There are known optimizations on the table for async functions especially around avoiding object allocation. Our implementation of async functions is significantly slower than other implementations. V8 has [recently implemented](https://codereview.chromium.org/2512103002/) an optimization that I think we could apply as... | Optimize async functions | https://api.github.com/repos/chakra-core/ChakraCore/issues/2055/comments | 1 | 2016-11-18T19:24:51Z | 2018-02-27T22:15:21Z | https://github.com/chakra-core/ChakraCore/issues/2055 | 190,400,924 | 2,055 |
[
"chakra-core",
"ChakraCore"
] | I have found that the Shared Debug library for linux does not work correctly. There is internal assert failures. The steps to reproduce are fairly straight forward if you follow the wiki with some slight changes( see: [Microsoft/ChakraCore Wiki: Embedding ChakraCore](https://github.com/Microsoft/ChakraCore/wiki/Embedd... | Linux: Shared Debug Library Broken | https://api.github.com/repos/chakra-core/ChakraCore/issues/2052/comments | 1 | 2016-11-18T02:26:58Z | 2016-11-19T14:36:58Z | https://github.com/chakra-core/ChakraCore/issues/2052 | 190,220,347 | 2,052 |
[
"chakra-core",
"ChakraCore"
] | We use double to store all FloatConstOpnd's in JIT.
While building a NAN float32 constant in IRBuilder we call:
`IR::FloatConstOpnd::New(constVal, TyFloat32, m_func), m_func);`
The function is declared as :
`FloatConstOpnd *
FloatConstOpnd::New(FloatConstType value, IRType type, Func *func)`
where `FloatCons... | WASM: float32 NAN value representation in JIT | https://api.github.com/repos/chakra-core/ChakraCore/issues/2049/comments | 3 | 2016-11-18T02:06:18Z | 2017-08-17T00:49:05Z | https://github.com/chakra-core/ChakraCore/issues/2049 | 190,217,734 | 2,049 |
[
"chakra-core",
"ChakraCore"
] | `(module (func (result i32)))` validates when it shouldn't | WASM - incorrectly validate function with return type with nothing in the type stack | https://api.github.com/repos/chakra-core/ChakraCore/issues/2048/comments | 5 | 2016-11-18T01:29:19Z | 2016-12-20T00:33:05Z | https://github.com/chakra-core/ChakraCore/issues/2048 | 190,213,072 | 2,048 |
[
"chakra-core",
"ChakraCore"
] | Implement LowererMD::IsOpndNegZero without a helper call | Lower IsOpndNegZero optimization (3d) | https://api.github.com/repos/chakra-core/ChakraCore/issues/2041/comments | 0 | 2016-11-17T21:20:29Z | 2017-05-04T22:45:58Z | https://github.com/chakra-core/ChakraCore/issues/2041 | 190,167,281 | 2,041 |
[
"chakra-core",
"ChakraCore"
] | This is sort of a big request, but fix compilation using GCC (version 5.4.0) on Ubuntu 16.04 LTS. Many Linux distributions use GCC as the default compiler.
| linux: Fix compile using GCC | https://api.github.com/repos/chakra-core/ChakraCore/issues/2038/comments | 9 | 2016-11-17T07:38:07Z | 2021-02-16T15:22:10Z | https://github.com/chakra-core/ChakraCore/issues/2038 | 189,964,287 | 2,038 |
[
"chakra-core",
"ChakraCore"
] | Add support to handle literals such as nan:0x0f1e2. The following tests for copysign and min/max are failing:
in `testsuite/float_misc.wast`
-noNative only:
(assert_return (invoke "f32.copysign" (f32.const nan:0x0f1e2) (f32.const nan)) (f32.const nan:0x0f1e2))
(assert_return (invoke "f32.copysign" (f32.const nan:... | WASM - handle float NAN literals | https://api.github.com/repos/chakra-core/ChakraCore/issues/2037/comments | 1 | 2016-11-17T05:57:23Z | 2017-08-17T00:49:13Z | https://github.com/chakra-core/ChakraCore/issues/2037 | 189,946,331 | 2,037 |
[
"chakra-core",
"ChakraCore"
] | Wrap WebAssembly Create in try/catch to catch WasmCompilationException and throw the proper javascript error | WASM - handle WasmCompilationException when instantiating | https://api.github.com/repos/chakra-core/ChakraCore/issues/2035/comments | 2 | 2016-11-17T02:33:50Z | 2017-02-01T00:56:05Z | https://github.com/chakra-core/ChakraCore/issues/2035 | 189,917,488 | 2,035 |
[
"chakra-core",
"ChakraCore"
] | WebAssembly.Module.imports resulting array should be in the same order as it was initially describe in the wasm section | WASM - WebAssembly.Module.imports keep order | https://api.github.com/repos/chakra-core/ChakraCore/issues/2034/comments | 0 | 2016-11-17T02:33:21Z | 2016-12-20T00:33:05Z | https://github.com/chakra-core/ChakraCore/issues/2034 | 189,917,404 | 2,034 |
[
"chakra-core",
"ChakraCore"
] | Fix WebAssembly.instantiate, Module.exports and Module.imports | WASM - js api bugs | https://api.github.com/repos/chakra-core/ChakraCore/issues/2033/comments | 0 | 2016-11-17T02:32:56Z | 2016-12-20T00:33:05Z | https://github.com/chakra-core/ChakraCore/issues/2033 | 189,917,334 | 2,033 |
[
"chakra-core",
"ChakraCore"
] | https://github.com/Microsoft/ChakraCore/wiki/Build-Status#legacy-builds
`
lib\Runtime\Library\WebAssemblyTable.cpp(124): error C2070: 'unknown': illegal sizeof operand [lib\Runtime\Library\Chakra.Runtime.Library.vcxproj]
`
`
lib\Runtime\Library\WebAssemblyTable.cpp(124): error C2338: sizeof(m_maxLength) == sizeo... | [Legacy] Illegal argument to sizeof | https://api.github.com/repos/chakra-core/ChakraCore/issues/2026/comments | 2 | 2016-11-16T01:48:24Z | 2016-12-15T23:08:42Z | https://github.com/chakra-core/ChakraCore/issues/2026 | 189,559,666 | 2,026 |
[
"chakra-core",
"ChakraCore"
] | As I mentioned in commit 0f69cba81b8fed268d2b6ac73a786778d8075741 of PR #2016, the TypedArray tests are cumbersome to work with and contain a lot of redundancy. It would be great to consolidate them into a single test file using UTF.js and looping through the different TypedArray constructors instead of repeating tests... | Clean up TypedArray tests (test/typedarray/*.js) | https://api.github.com/repos/chakra-core/ChakraCore/issues/2020/comments | 0 | 2016-11-15T19:49:36Z | 2018-02-27T22:17:26Z | https://github.com/chakra-core/ChakraCore/issues/2020 | 189,488,565 | 2,020 |
[
"chakra-core",
"ChakraCore"
] | Effectively, 'new Uint8Array(0)' and 'new Uint8Array()' and 'new Uint8Array(undefined)' should have the same behavior.
Converting from an internal issue.
This issue is not a spec deviation from ES 6.0. It's a spec change in ES 2017. In ES6, we were supposed to (and are correctly) throwing TypeError if length is u... | TypedArray constructor throws TypeError for undefined argument | https://api.github.com/repos/chakra-core/ChakraCore/issues/2014/comments | 2 | 2016-11-15T01:32:38Z | 2016-11-17T19:37:55Z | https://github.com/chakra-core/ChakraCore/issues/2014 | 189,275,384 | 2,014 |
[
"chakra-core",
"ChakraCore"
] | The Error/stack.js test fails because all the "finally" blocks are not executed (as of git master bbf46243132). I can reduce the issue to just this code
```javascript
try {
try {
throw 42;
} finally {
print("In finally");
}
}
catch (e) {
print("In catch", e.description);
}
``... | jit: finally block is not executed after try/catch throws exception | https://api.github.com/repos/chakra-core/ChakraCore/issues/2009/comments | 15 | 2016-11-14T18:44:13Z | 2017-01-05T08:08:28Z | https://github.com/chakra-core/ChakraCore/issues/2009 | 189,191,809 | 2,009 |
[
"chakra-core",
"ChakraCore"
] | JsRunScriptUtf8 is missing from the Master branch, which is used in all of the samples for Linux. I guess previously there was a Linux branch and currently it's not there.
Could you please add this? or change the example program to use current exposed API? | JsRunScriptUtf8 missing | https://api.github.com/repos/chakra-core/ChakraCore/issues/2006/comments | 4 | 2016-11-14T14:19:25Z | 2016-11-15T09:24:28Z | https://github.com/chakra-core/ChakraCore/issues/2006 | 189,123,330 | 2,006 |
[
"chakra-core",
"ChakraCore"
] | I see the same source file I had cleaned up from white spaces is now with of new whitespaces.
It is really hard to see what was changed with the commit due to white-space noise.
We might introduce `git diff --check` or something similar to limit whitespace noise.
| Introduce git diff --check or something similar | https://api.github.com/repos/chakra-core/ChakraCore/issues/2004/comments | 27 | 2016-11-14T12:15:23Z | 2017-03-10T08:20:22Z | https://github.com/chakra-core/ChakraCore/issues/2004 | 189,098,046 | 2,004 |
[
"chakra-core",
"ChakraCore"
] | We could have `test flag` options are available to our xplat `ch` release.
I don't see any reason to include `debug dump` related functionality to that binary. My intention is to support test flags without hurting the performance of the binary.
Looked through the source codes and saw `ENABLE_DEBUG_CONFIG_OPTIONS` ... | Fix ENABLE_DEBUG_CONFIG_OPTIONS usage | https://api.github.com/repos/chakra-core/ChakraCore/issues/2003/comments | 1 | 2016-11-14T09:42:17Z | 2017-09-13T01:08:47Z | https://github.com/chakra-core/ChakraCore/issues/2003 | 189,067,284 | 2,003 |
[
"chakra-core",
"ChakraCore"
] | I see that the latest JSRT code ``master`` branch has a different API than what is documented in the [wiki](https://github.com/Microsoft/ChakraCore/wiki/JavaScript-Runtime-%28JSRT%29-Reference). Notably ``JsStringToPointer()`` no longer exist but there are functions like ``JsCopyString()`` which use utf-8 instead. Th... | New JSRT API documentation | https://api.github.com/repos/chakra-core/ChakraCore/issues/2002/comments | 5 | 2016-11-14T01:10:17Z | 2016-11-16T01:43:26Z | https://github.com/chakra-core/ChakraCore/issues/2002 | 189,009,541 | 2,002 |
[
"chakra-core",
"ChakraCore"
] | Make imported int64 globals throw at instantiation time instead of compile time | WASM - Int64 imported global error | https://api.github.com/repos/chakra-core/ChakraCore/issues/1996/comments | 0 | 2016-11-12T01:12:23Z | 2016-12-20T00:33:05Z | https://github.com/chakra-core/ChakraCore/issues/1996 | 188,882,684 | 1,996 |
[
"chakra-core",
"ChakraCore"
] | Known place that needs updating
- LowererMDArch::LowerWasmMemOp
- trunc and div/rem | WASM - Use WebAssembly.RuntimeError where needed | https://api.github.com/repos/chakra-core/ChakraCore/issues/1991/comments | 0 | 2016-11-11T22:10:18Z | 2016-12-20T00:33:05Z | https://github.com/chakra-core/ChakraCore/issues/1991 | 188,862,096 | 1,991 |
[
"chakra-core",
"ChakraCore"
] | Getting this in debug builds with clang 3.9.1:
/home/xan/git/ChakraCore/lib/Runtime/ByteCode/ByteCodeDumper.cpp:1192:21: error: definition with same mangled name as another definition
ByteCodeDumper::DumpReg2(OpCode op, const unaligned T * data, FunctionBody * dumpFunction, ByteCodeReader& reader)
... | Mangled name collision with clang 3.9.1 | https://api.github.com/repos/chakra-core/ChakraCore/issues/1989/comments | 1 | 2016-11-11T19:33:39Z | 2016-11-14T21:18:12Z | https://github.com/chakra-core/ChakraCore/issues/1989 | 188,833,400 | 1,989 |
[
"chakra-core",
"ChakraCore"
] | I have a page (parent.html) that opens another page (child.html) in a new window. That child page calls a function that was defined globally in its opener, passing in an array. In that function, a new Set is created, passing the array received from the child window to the Set constructor. This leads to the error "SCRIP... | "SCRIPT5002: Function expected" when passing array from other window to Set constructor | https://api.github.com/repos/chakra-core/ChakraCore/issues/1987/comments | 4 | 2016-11-11T14:18:16Z | 2016-11-19T01:29:20Z | https://github.com/chakra-core/ChakraCore/issues/1987 | 188,769,341 | 1,987 |
[
"chakra-core",
"ChakraCore"
] | The following tests are failing in jitted code
`test/WasmSpec/testsuite/conversions.wast` lines 266 & 268
`test/WasmSpec/testsuite/float_exprs.wast` lines 493 & 698-700 | WASM - f32.convert_u/i32 bugs | https://api.github.com/repos/chakra-core/ChakraCore/issues/1967/comments | 5 | 2016-11-09T20:57:50Z | 2016-12-20T00:33:05Z | https://github.com/chakra-core/ChakraCore/issues/1967 | 188,350,702 | 1,967 |
[
"chakra-core",
"ChakraCore"
] | Wrong behavior in jitted code for i32.trunc_u/f32 and i32.trunc_u/f64
See test/WasmSpec/conversions.wast lines 78-84 and 117-122
test/WasmSpec/float_exprs.wast lines 695-696
test/WasmSpec/float_exprs.wast lines 704-709 | WASM - int32 trunc bug | https://api.github.com/repos/chakra-core/ChakraCore/issues/1957/comments | 6 | 2016-11-08T23:56:17Z | 2016-12-20T00:33:05Z | https://github.com/chakra-core/ChakraCore/issues/1957 | 188,136,701 | 1,957 |
[
"chakra-core",
"ChakraCore"
] | f32.min and f32.max invalid result with `-0` depending if it's the 1st or 2nd argument.
Also different behavior between interpreter and Jit.
See
test/WasmSpec/testsuite/f32.wast:1318
test/WasmSpec/testsuite/f32.wast:1642
test/WasmSpec/testsuite/f64.wast:1318
test/WasmSpec/testsuite/f64.wast:1643 | WASM - f32/f64.min/max -0 bug | https://api.github.com/repos/chakra-core/ChakraCore/issues/1954/comments | 1 | 2016-11-08T21:19:58Z | 2016-12-20T00:33:05Z | https://github.com/chakra-core/ChakraCore/issues/1954 | 188,106,221 | 1,954 |
[
"chakra-core",
"ChakraCore"
] | Implement i32.Wrap/i64 operator
C++ equivalent to `int32 result = (int32)someInt64Val;` | WASM - i32.Wrap/i64 | https://api.github.com/repos/chakra-core/ChakraCore/issues/1946/comments | 1 | 2016-11-08T02:46:45Z | 2016-12-20T00:33:05Z | https://github.com/chakra-core/ChakraCore/issues/1946 | 187,887,967 | 1,946 |
[
"chakra-core",
"ChakraCore"
] | Proposed in #1802 | Use /Zc:strictStrings flag in VC builds. | https://api.github.com/repos/chakra-core/ChakraCore/issues/1942/comments | 3 | 2016-11-08T00:49:48Z | 2020-03-31T15:16:44Z | https://github.com/chakra-core/ChakraCore/issues/1942 | 187,872,145 | 1,942 |
[
"chakra-core",
"ChakraCore"
] | I've found that when saying `test Ubuntu ubuntu_linux_release_static`, both `ubuntu_linux_release_static` and `Ubuntu ubuntu_linux_release` get rerun. | dotnet-bot seems to test everything that has substring of your request | https://api.github.com/repos/chakra-core/ChakraCore/issues/1933/comments | 12 | 2016-11-07T19:23:33Z | 2017-03-02T11:41:34Z | https://github.com/chakra-core/ChakraCore/issues/1933 | 187,803,185 | 1,933 |
[
"chakra-core",
"ChakraCore"
] | Steps to reproduce
---
Execute build steps as documented here:
https://github.com/Microsoft/ChakraCore/wiki/Building-ChakraCore
Replacing
```
git checkout linux
```
with
```
git checkout release/1.3
```
Expected Behavior
---
Successful build of ChakraCore on macOS
Actual Behavior
---
The bui... | Build on macOS 10.12 fails due to deprecated system call | https://api.github.com/repos/chakra-core/ChakraCore/issues/1927/comments | 1 | 2016-11-06T15:51:23Z | 2016-11-07T05:16:33Z | https://github.com/chakra-core/ChakraCore/issues/1927 | 187,569,420 | 1,927 |
[
"chakra-core",
"ChakraCore"
] | Hi,
We found an odd crash of the ChakraCore interpreter (ch) when you "throw a float". It was tested in ArchLinux using revision 627e01bc65455b2dad495bd311a2eced7417e97f.
To reproduce:
```
$ echo "throw 1.1;" > sigill.js
$ gdb --args ./ch sigill.js
...
Thread 1 "ch" received signal SIGILL, Illegal instructi... | SIGILL when throwing an exception | https://api.github.com/repos/chakra-core/ChakraCore/issues/1922/comments | 6 | 2016-11-04T23:24:36Z | 2016-11-07T06:41:25Z | https://github.com/chakra-core/ChakraCore/issues/1922 | 187,459,010 | 1,922 |
[
"chakra-core",
"ChakraCore"
] | Some JSRT API accept `char` for Utf8 named functions while others `uint8_t`.
We had a small discussion on this. Shared my opinion below;
- `char` is more developer friendly and all C / IO comes with `char`.
If a developer has nothing to do with utf8 encoding / flags etc.
there is no reason for her/hi... | JSRT: uint8_t vs char for Utf8 interface | https://api.github.com/repos/chakra-core/ChakraCore/issues/1918/comments | 8 | 2016-11-04T05:22:05Z | 2016-12-27T18:34:23Z | https://github.com/chakra-core/ChakraCore/issues/1918 | 187,256,110 | 1,918 |
[
"chakra-core",
"ChakraCore"
] | Only few of our callbacks can execute JSRT API calls. i.e. new `JsSerializedLoadScriptCallback` is one of them. https://github.com/Microsoft/ChakraCore/blob/master/lib/Jsrt/JsrtSourceHolder.cpp#L246-L252
Is there any particular callback we shouldn't allow JSRT API calls ? or best if we make them all capable of doin... | JSRT: Inconsistent Callback behavior | https://api.github.com/repos/chakra-core/ChakraCore/issues/1917/comments | 10 | 2016-11-04T05:09:33Z | 2018-03-17T01:27:04Z | https://github.com/chakra-core/ChakraCore/issues/1917 | 187,254,966 | 1,917 |
[
"chakra-core",
"ChakraCore"
] | The start function must not take any arguments | WASM - Validate Start Function | https://api.github.com/repos/chakra-core/ChakraCore/issues/1901/comments | 0 | 2016-11-02T01:45:49Z | 2016-12-20T00:33:05Z | https://github.com/chakra-core/ChakraCore/issues/1901 | 186,692,594 | 1,901 |
[
"chakra-core",
"ChakraCore"
] | For i64.div/rem add checks to handle DivideByZero, IntegerOverflow
| WASM - Int64 Math Traps | https://api.github.com/repos/chakra-core/ChakraCore/issues/1900/comments | 1 | 2016-11-02T00:11:46Z | 2016-12-20T00:33:04Z | https://github.com/chakra-core/ChakraCore/issues/1900 | 186,681,790 | 1,900 |
[
"chakra-core",
"ChakraCore"
] | ```js
(function() {
var v = new Int8Array(2);
v[1] = 31;
Object.defineProperty(v, 'length', {value : 4});
var ret = v.toLocaleString()
console.log(ret);
})();
```
toLocaleString should iterate over the length we got from internal slot of typed array instead of Get('length')
Expected
```... | TypedArray : toLocaleString should use length from internal slot | https://api.github.com/repos/chakra-core/ChakraCore/issues/1896/comments | 0 | 2016-11-01T21:16:37Z | 2016-12-22T02:12:50Z | https://github.com/chakra-core/ChakraCore/issues/1896 | 186,649,672 | 1,896 |
[
"chakra-core",
"ChakraCore"
] | When importing a WebAssembly function into another module, that function needs to be called without boxing/unboxing.
The main reason is to support types that are not supported by javascript.
The solution we came up with is to create a wasm thunk (similar to #1807) that will then call the import and put this in the ... | WASM - Treat imported WebAssembly functions as internal functions | https://api.github.com/repos/chakra-core/ChakraCore/issues/1895/comments | 0 | 2016-11-01T20:44:21Z | 2016-12-20T00:33:04Z | https://github.com/chakra-core/ChakraCore/issues/1895 | 186,641,942 | 1,895 |
[
"chakra-core",
"ChakraCore"
] | ```js
(function() {
var arr = [11, 22, 33, 44];
var first = true;
arr.reduce(function (a1, a2, a3, a4) {
if (first) {
first = false;
Object.defineProperty(arr, '2', { get : function() {
return 201;
}});
}
console.log(a2);... | Changing array to es5array on array method does not give correct output. | https://api.github.com/repos/chakra-core/ChakraCore/issues/1893/comments | 2 | 2016-11-01T18:17:41Z | 2017-02-04T01:52:26Z | https://github.com/chakra-core/ChakraCore/issues/1893 | 186,607,093 | 1,893 |
[
"chakra-core",
"ChakraCore"
] | Hi, what is the state of C# -> WASM toolchain using Microsoft tools such as Visual Studio? Thanks. | WASM - C# toolchain? | https://api.github.com/repos/chakra-core/ChakraCore/issues/1891/comments | 12 | 2016-11-01T09:53:36Z | 2016-12-20T00:33:04Z | https://github.com/chakra-core/ChakraCore/issues/1891 | 186,496,049 | 1,891 |
[
"chakra-core",
"ChakraCore"
] | Related #1852
We want to calculate const math in the backend if possible.
Make sure the operators that differ from javascript are correctly handled | WASM - Fold const math operations (5d) | https://api.github.com/repos/chakra-core/ChakraCore/issues/1889/comments | 0 | 2016-10-31T22:37:13Z | 2017-05-04T01:14:52Z | https://github.com/chakra-core/ChakraCore/issues/1889 | 186,417,501 | 1,889 |
[
"chakra-core",
"ChakraCore"
] | Use the fast array implementation to detect out of bounds access and trap. | WASM - fast array out of bounds traps | https://api.github.com/repos/chakra-core/ChakraCore/issues/1888/comments | 0 | 2016-10-31T22:36:18Z | 2017-02-17T02:32:26Z | https://github.com/chakra-core/ChakraCore/issues/1888 | 186,417,331 | 1,888 |
[
"chakra-core",
"ChakraCore"
] | Add support for int64 and float32 arguments when calling imports
Depends on #1895 | WASM - Int64/Float32 support in call import | https://api.github.com/repos/chakra-core/ChakraCore/issues/1887/comments | 0 | 2016-10-31T22:35:31Z | 2016-12-20T00:33:04Z | https://github.com/chakra-core/ChakraCore/issues/1887 | 186,417,211 | 1,887 |
[
"chakra-core",
"ChakraCore"
] | The following asserts at this time.
```js
print(Wasm.instantiateModule(buffer, ffi).exports.a);
```
Investigate and fix the bug | WASM - assert when printing functions | https://api.github.com/repos/chakra-core/ChakraCore/issues/1886/comments | 0 | 2016-10-31T22:34:46Z | 2016-12-20T00:33:04Z | https://github.com/chakra-core/ChakraCore/issues/1886 | 186,417,096 | 1,886 |
[
"chakra-core",
"ChakraCore"
] | Setup tools to test and make sure the wasm frontend is secure | WASM - Security analysis (2w) | https://api.github.com/repos/chakra-core/ChakraCore/issues/1885/comments | 2 | 2016-10-31T22:33:56Z | 2017-05-03T23:19:26Z | https://github.com/chakra-core/ChakraCore/issues/1885 | 186,416,978 | 1,885 |
[
"chakra-core",
"ChakraCore"
] | Implement the final javascript API for the MVP | WASM - Async Javascript API | https://api.github.com/repos/chakra-core/ChakraCore/issues/1884/comments | 0 | 2016-10-31T22:32:48Z | 2016-12-20T00:33:04Z | https://github.com/chakra-core/ChakraCore/issues/1884 | 186,416,794 | 1,884 |
[
"chakra-core",
"ChakraCore"
] | We won't support debugging right now, but we need to make sure we don't crash when opening the debugger. | WASM - Investigate Debugging/Profiling scenario on Edge | https://api.github.com/repos/chakra-core/ChakraCore/issues/1883/comments | 2 | 2016-10-31T22:32:02Z | 2016-12-20T00:33:04Z | https://github.com/chakra-core/ChakraCore/issues/1883 | 186,416,578 | 1,883 |
[
"chakra-core",
"ChakraCore"
] | We should make a copy of the binary buffer and use this for compilation instead of the source.
The reason is the source can be modified between the time it is passed and when we do the actual compilation. | WASM - Copy binary buffer | https://api.github.com/repos/chakra-core/ChakraCore/issues/1882/comments | 1 | 2016-10-31T22:31:20Z | 2016-12-20T00:33:04Z | https://github.com/chakra-core/ChakraCore/issues/1882 | 186,416,427 | 1,882 |
[
"chakra-core",
"ChakraCore"
] | Until we have debugging support, we should ignore that section. | WASM - Ignore names section | https://api.github.com/repos/chakra-core/ChakraCore/issues/1881/comments | 0 | 2016-10-31T22:30:09Z | 2016-12-20T00:33:04Z | https://github.com/chakra-core/ChakraCore/issues/1881 | 186,416,221 | 1,881 |
[
"chakra-core",
"ChakraCore"
] | Trap on invalid indirect call (out of bounds and invalid signature) | WASM - Indirect call trap | https://api.github.com/repos/chakra-core/ChakraCore/issues/1879/comments | 0 | 2016-10-31T22:29:23Z | 2016-12-20T00:33:04Z | https://github.com/chakra-core/ChakraCore/issues/1879 | 186,416,094 | 1,879 |
[
"chakra-core",
"ChakraCore"
] | Verify and implement math operators that need to trap
https://github.com/WebAssembly/design/blob/binary_0xc/AstSemantics.md#32-bit-integer-operators | WASM - Int32 Math and conversion traps | https://api.github.com/repos/chakra-core/ChakraCore/issues/1878/comments | 8 | 2016-10-31T22:27:51Z | 2016-12-20T00:33:03Z | https://github.com/chakra-core/ChakraCore/issues/1878 | 186,415,815 | 1,878 |
[
"chakra-core",
"ChakraCore"
] | Throw trap when doing out of bounds access | WASM - Array access out of bounds | https://api.github.com/repos/chakra-core/ChakraCore/issues/1877/comments | 0 | 2016-10-31T22:27:11Z | 2016-12-20T00:33:03Z | https://github.com/chakra-core/ChakraCore/issues/1877 | 186,415,680 | 1,877 |
[
"chakra-core",
"ChakraCore"
] | Support exporting the table our of the wasm module
https://github.com/WebAssembly/design/blob/binary_0xc/BinaryEncoding.md#export-entry | WASM - Export Table | https://api.github.com/repos/chakra-core/ChakraCore/issues/1876/comments | 0 | 2016-10-31T22:26:23Z | 2016-12-20T00:33:26Z | https://github.com/chakra-core/ChakraCore/issues/1876 | 186,415,538 | 1,876 |
[
"chakra-core",
"ChakraCore"
] | Support importing memory object to the wasm module
https://github.com/WebAssembly/design/blob/binary_0xc/BinaryEncoding.md#import-entry
| WASM - Import Memory | https://api.github.com/repos/chakra-core/ChakraCore/issues/1875/comments | 2 | 2016-10-31T22:25:55Z | 2016-12-20T00:33:26Z | https://github.com/chakra-core/ChakraCore/issues/1875 | 186,415,441 | 1,875 |
[
"chakra-core",
"ChakraCore"
] | Support importing a table to the wasm module
depends on new Js API
https://github.com/WebAssembly/design/blob/binary_0xc/BinaryEncoding.md#import-entry | WASM - Import table | https://api.github.com/repos/chakra-core/ChakraCore/issues/1874/comments | 0 | 2016-10-31T22:25:26Z | 2016-12-20T00:33:26Z | https://github.com/chakra-core/ChakraCore/issues/1874 | 186,415,360 | 1,874 |
[
"chakra-core",
"ChakraCore"
] | Correctly call imported functions from the function table (intermediary function used for the conversion) | WASM - Imported function in the table | https://api.github.com/repos/chakra-core/ChakraCore/issues/1873/comments | 1 | 2016-10-31T22:24:13Z | 2016-12-20T00:33:26Z | https://github.com/chakra-core/ChakraCore/issues/1873 | 186,415,100 | 1,873 |
[
"chakra-core",
"ChakraCore"
] | Support globals to define the offset of the elements segment
https://github.com/WebAssembly/design/blob/binary_0xc/BinaryEncoding.md#element-section
| WASM - Elements segments Init Expression | https://api.github.com/repos/chakra-core/ChakraCore/issues/1872/comments | 0 | 2016-10-31T22:23:48Z | 2016-12-20T00:33:26Z | https://github.com/chakra-core/ChakraCore/issues/1872 | 186,415,029 | 1,872 |
[
"chakra-core",
"ChakraCore"
] | Implement operator i64.reinterpret/f64 | WASM - i64.reinterpret/f64 | https://api.github.com/repos/chakra-core/ChakraCore/issues/1871/comments | 0 | 2016-10-31T22:22:08Z | 2016-12-20T00:33:26Z | https://github.com/chakra-core/ChakraCore/issues/1871 | 186,414,723 | 1,871 |
[
"chakra-core",
"ChakraCore"
] | Implement operator f64.reinterpret/i64 | WASM - f64.reinterpret/i64 | https://api.github.com/repos/chakra-core/ChakraCore/issues/1870/comments | 0 | 2016-10-31T22:21:46Z | 2016-12-20T00:33:26Z | https://github.com/chakra-core/ChakraCore/issues/1870 | 186,414,658 | 1,870 |
[
"chakra-core",
"ChakraCore"
] | Implement operator f64.convert_u/i64 | WASM - f64.convert_u/i64 | https://api.github.com/repos/chakra-core/ChakraCore/issues/1869/comments | 0 | 2016-10-31T22:21:26Z | 2016-12-20T00:33:26Z | https://github.com/chakra-core/ChakraCore/issues/1869 | 186,414,605 | 1,869 |
[
"chakra-core",
"ChakraCore"
] | Implement operator f64.convert_s/i64 | WASM - f64.convert_s/i64 | https://api.github.com/repos/chakra-core/ChakraCore/issues/1868/comments | 0 | 2016-10-31T22:21:08Z | 2016-12-20T00:33:26Z | https://github.com/chakra-core/ChakraCore/issues/1868 | 186,414,537 | 1,868 |
[
"chakra-core",
"ChakraCore"
] | Implement operator f32.convert_u/i64 | WASM - f32.convert_u/i64 | https://api.github.com/repos/chakra-core/ChakraCore/issues/1867/comments | 0 | 2016-10-31T22:20:50Z | 2016-12-20T00:33:26Z | https://github.com/chakra-core/ChakraCore/issues/1867 | 186,414,480 | 1,867 |
[
"chakra-core",
"ChakraCore"
] | Implement operator f32.convert_s/i64 | WASM - f32.convert_s/i64 | https://api.github.com/repos/chakra-core/ChakraCore/issues/1866/comments | 0 | 2016-10-31T22:20:27Z | 2016-12-20T00:33:26Z | https://github.com/chakra-core/ChakraCore/issues/1866 | 186,414,403 | 1,866 |
[
"chakra-core",
"ChakraCore"
] | Implement operator i64.extend_u/i32 | WASM - i64.extend_u/i32 | https://api.github.com/repos/chakra-core/ChakraCore/issues/1865/comments | 1 | 2016-10-31T22:20:11Z | 2016-12-20T00:33:25Z | https://github.com/chakra-core/ChakraCore/issues/1865 | 186,414,358 | 1,865 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.