| /arkcompiler/ets_runtime/test/sharedtest/check/ |
| D | expect_output.txt | 8 # Unless required by applicable law or agreed to in writing, software
17 Success update propString to null with stobjbyname
18 Success update subClassPropSendable to null with stobjbyname
19 Fail to update propNumber to null with stobjbyname. err: TypeError: Cannot set sendable property wi…
20 Fail to update propNumber to null with stobjbyname. err: TypeError: Cannot set sendable property wi…
22 Fail to update propString to undefined with stobjbyname. err: TypeError: Cannot set sendable proper…
23 Fail to update subClassPropSendable to undefined with stobjbyname. err: TypeError: Cannot set senda…
24 Fail to update propNumber to undefined with stobjbyname. err: TypeError: Cannot set sendable proper…
25 Fail to update propNumber to undefined with stobjbyname. err: TypeError: Cannot set sendable proper…
28 Fail to update subClassPropString with stobjbyname. err: TypeError: Cannot set sendable property wi…
[all …]
|
| D | sharedcheck.ts | 9 * Unless required by applicable law or agreed to in writing, software
32 * Unless required by applicable law or agreed to in writing, software
117 print("Fail to delete propNumber. err: " + error)
125 print("Success to extend prop with defineProperty")
127 print("Fail to extend prop with defineProperty. err: " + error);
134 print("Fail to extend prop1 with defineProperty. err: " + error)
141 print("Fail to extend prop2 with defineProperties. err: " + error)
148 print("Fail to extend prop3 with stobjbyname. err: " + error)
158 print("Fail to replace instance's func. err: " + error);
168 print("Fail to update prototype. err: " + error)
[all …]
|
| /arkcompiler/ets_frontend/ets2panda/linter-4.2/test/ |
| D | structural_identity.ts | 9 * Unless required by applicable law or agreed to in writing, software
115 fDC(c); // OK, assignment to dynamic
116 fDC(i); // OK, assignment to dynamic
117 fDC(ci); // OK, assignment to dynamic
118 fDC(cc); // OK, assignment to dynamic
119 fDC(ii); // OK, assignment to dynamic
120 fDI(c); // OK, assignment to dynamic
121 fDI(i); // OK, assignment to dynamic
122 fDI(ci); // OK, assignment to dynamic
123 fDI(cc); // OK, assignment to dynamic
[all …]
|
| /arkcompiler/ets_frontend/ets2panda/linter/test/ |
| D | structural_identity.ts | 9 * Unless required by applicable law or agreed to in writing, software
115 fDC(c); // OK, assignment to dynamic
116 fDC(i); // OK, assignment to dynamic
117 fDC(ci); // OK, assignment to dynamic
118 fDC(cc); // OK, assignment to dynamic
119 fDC(ii); // OK, assignment to dynamic
120 fDI(c); // OK, assignment to dynamic
121 fDI(i); // OK, assignment to dynamic
122 fDI(ci); // OK, assignment to dynamic
123 fDI(cc); // OK, assignment to dynamic
[all …]
|
| /arkcompiler/runtime_core/static_core/plugins/ets/stdlib/std/core/ |
| D | Console.ets | 9 * Unless required by applicable law or agreed to in writing, software
19 * Standard console, that provides access to standard output stream
25 * Prints an object to the console
27 * @param i value to print
35 * Prints a string to the console
37 * @param i value to print
42 * Prints a boolean to the console
44 * @param i value to print
49 * Prints a byte to the console
51 * @param i value to print
[all …]
|
| D | StringBuilder.ets | 9 * Unless required by applicable law or agreed to in writing, software
24 …private buf: Object[] = new Object[StringBuilder.INITIAL_BUF_SIZE]; // array with pointers to stri…
37 * @param fromChars array that will be used to initialize the builder
51 * @param s string that will be used to initialize the builder
73 * Appends an object representation as string to the builder's internal buffer
75 * @param o object that will be converted to a string
85 * Appends a string to the builder's internal buffer
87 * @param s string to be appended
94 * Appends a boolean as string to the builder's internal buffer
96 * @param i value to be appended
[all …]
|
| /arkcompiler/runtime_core/static_core/docs/ |
| D | doxygen.config | 3 # This file describes the settings to be used by the documentation system
37 # The PROJECT_NUMBER tag can be used to enter a project or revision number. This
52 # the logo to the output directory.
56 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path
58 # entered, it will be relative to the location where doxygen was started. If
63 # If the CREATE_SUBDIRS tag is set to YES then doxygen will create 4096 sub-
73 # If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII
74 # characters to appear in the names of generated files. If set to NO, non-ASCII
81 # The OUTPUT_LANGUAGE tag is used to specify the language in which all
83 # information to generate all constant output in the proper language.
[all …]
|
| D | rationale-for-bytecode.md | 26 Here comes the bytecode. Simply said, it is an attempt to build an abstract CPU on top of real
28 special program called _interpreter_. The goal of the interpreter is to read our unified _virtual_
30 making interpretation slower than _native code execution_. In return, we get the ability to
38 to distinguish between an abstract system and the hardware.
45 One very important question is how an operation refers to its operands.
52 push_arg1 ; copy the first argument to the top of the stack
53 push_arg2 ; copy the second argument to the top of stack
74 require up to 4 bytes to encode.
76 At the same time, to execute a stack-based addition we need to run 3 instructions compared to
77 just a single register-based instruction. Since the interpreter has an extra work to do to read
[all …]
|
| D | runtime-compiled_code-interaction.md | 9 * Transition from the interpeter to compiled code and vise versa
17 Panda runtime as a set of functions aimed to execute managed code. The runtime consists of several …
18 The document refers to the interpreter and the compiler modules.
20 …rpreter is a part of the runtime aimed to execute bytecode of managed functions. The interpreter i…
23 The compiler is aimed to translate managed function's bytecode to native code. The compiler has an …
25 changes its entrypoint to newly generated code. Next time when the function gets called native code…
28 Panda runtime and managed code must call functions according to the target calling convention.
29 Compiled code of a managed function must accept one extra argument: the pointer to `panda::Method` …
36 - a pointer to `panda::Method` in the register R0.
46 The result of call is placed according to the target calling convention.
[all …]
|
| D | file_format.md | 6 * Support for fast access to information.
13 doesn't fit in 16-bit unsigned integer. It leads to application developer have to create several
16 Current binary file format should extend these limits to conform to the modern requirements.
18 To achieve this, all references in the binary file are 4 bytes long. It allows to have 4Gb for
21 The format uses [TaggedValue](#taggedvalue) which allows to store only information we have and
22 avoid 0 offsets to absent information.
24 But to achieve more compactness 16-bit indexes are used to refer classes, methods and fields in
30 Binary file format should support fast access to information. It means that
33 a sorted list of offsets to classes. This index is compact and allows to find a type definition
40 having an offset to an entity it doesn't matter whether the entity is local or foreign.
[all …]
|
| D | design-of-interpreter.md | 11 | Requirements | Enlists the requirements to the component. |
12 | Key Design Decisions | Summarizes the key decisions to address the requirements. |
16 Please refer to the [glossary](glossary.md) for terminology clarification.
23 1. The platform should scale from microcontrollers to hi-end mobile phones:
25 1. It should be able to run consuming 64Kb of RAM.
33 1. Bytecode should allow the interpreter to run no slower than state of the art interpreters.
34 1. Bytecode should be compact in size to avoid bloating application code.
35 1. Bytecode description should have a single entry point to simplify maintenance
40 1. Bytecode is register-based: all arguments and variables are mapped to virtual registers,
58 * Converter from bytecode to the compiler's intermediate representation is partially implemented
[all …]
|
| /arkcompiler/runtime_core/docs/ |
| D | doxygen.config | 3 # This file describes the settings to be used by the documentation system
37 # The PROJECT_NUMBER tag can be used to enter a project or revision number. This
52 # the logo to the output directory.
56 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path
58 # entered, it will be relative to the location where doxygen was started. If
63 # If the CREATE_SUBDIRS tag is set to YES then doxygen will create 4096 sub-
73 # If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII
74 # characters to appear in the names of generated files. If set to NO, non-ASCII
81 # The OUTPUT_LANGUAGE tag is used to specify the language in which all
83 # information to generate all constant output in the proper language.
[all …]
|
| D | runtime-compiled_code-interaction.md | 9 * Transition from the interpeter to compiled code and vise versa
17 Panda runtime as a set of functions aimed to execute managed code. The runtime consists of several …
18 The document refers to the interpreter and the compiler modules.
20 …rpreter is a part of the runtime aimed to execute bytecode of managed functions. The interpreter i…
23 The compiler is aimed to translate managed function's bytecode to native code. The compiler has an …
25 changes its entrypoint to newly generated code. Next time when the function gets called native code…
28 Panda runtime and managed code must call functions according to the target calling convention.
29 Compiled code of a managed function must accept one extra argumnent: the pointer to `panda::Method`…
36 - a pointer to `panda::Method` in the register R0.
48 | pending_exception_ | panda::ObjectHeader* | A pointer to a thrown exception or 0 if there is n…
[all …]
|
| D | rationale-for-bytecode.md | 26 Here comes the bytecode. Simply said, it is an attempt to build an abstract CPU on top of real
28 special program called _interpreter_. The goal of the interpreter is to read our unified _virtual_
30 making interpretation slower than _native code execution_. In return, we get the ability to
38 to distinguish between an abstract system and the hardware.
45 One very important question is how an operation refers to its operands.
52 push_arg1 ; copy the first argument to the top of the stack
53 push_arg2 ; copy the second argument to the top of stack
74 require up to 4 bytes to encode.
76 At the same time, to execute a stack-based addition we need to run 3 instructions compared to
77 just a single register-based instruction. Since the interpreter has an extra work to do to read
[all …]
|
| D | file_format.md | 6 * Support for fast access to information.
13 doesn't fit in 16-bit unsigned integer. It leads to application developer have to create several
16 Current binary file format should extend these limits to conform to the modern requirements.
18 To achieve this, all references in the binary file are 4 bytes long. It allows to have 4Gb for
21 The format uses [TaggedValue](#taggedvalue) which allows to store only information we have and
22 avoid 0 offsets to absent information.
24 But to achieve more compactness 16-bit indexes are used to refer classes, methods and fields in
30 Binary file format should support fast access to information. It means that
33 a sorted list of offsets to classes. This index is compact and allows to find a type definition
40 having an offset to an entity it doesn't matter whether the entity is local or foreign.
[all …]
|
| D | design-of-interpreter.md | 11 | Requirements | Enlists the requirements to the component. |
12 | Key Design Decisions | Summarizes the key decisions to address the requirements. |
16 Please refer to the [glossary](glossary.md) for terminology clarification.
23 1. The platform should scale from microcontrollers to hi-end mobile phones:
25 1. It should be able to run consuming 64Kb of RAM.
33 1. Bytecode should allow the interpreter to run no slower than state of the art interpreters.
34 1. Bytecode should be compact in size to avoid bloating application code.
35 1. Bytecode description should have a single entry point to simplify maintenance
40 1. Bytecode is register-based: all arguments and variables are mapped to virtual registers,
58 * Converter from bytecode to the compiler's intermediate representation is partially implemented
[all …]
|
| D | ir_format.md | 4 * Possibility to implement various optimizations and analyses
8 * Be able to convert to other IR and back
12 …to have auxiliary functionality for various code transformations and analyses. The structure of th…
14 … to be able to change the order of the passes, add and delete passes(If 2 passes have a dependency…
15 Second, we need to support the transfer of information between optimizations.
45 The benefits of some optimizations are not obvious or do need profiling information to implement th…
51 !NOTE It is possible to write other optimizations based on the specifics of the language and VM
55 We will try to make it possible to pass optimizations in an arbitrary order. Some restrictions will…
61 * Converting to LLVM IR
63 * Common properties will be introduced for the instructions, making it easier to add new instructio…
[all …]
|
| /arkcompiler/ets_frontend/ts2panda/tests/ |
| D | scope.test.ts | 9 * Unless required by applicable law or agreed to in writing, software
32 it("test add 'none' variable to GlobalScope", function () {
35 expect(variable instanceof GlobalVariable).to.be.true;
37 expect(outVariable === variable).to.be.true;
38 expect(lv).to.be.equal(0);
39 expect(sp).to.be.equal(scope);
42 it("test add 'var' variable to GlobalScope", function () {
45 expect(variable instanceof GlobalVariable).to.be.true;
47 expect(outVariable === variable).to.be.true;
48 expect(lv).to.be.equal(0);
[all …]
|
| /arkcompiler/runtime_core/static_core/tests/cts-assembly/ |
| D | floatcast-test-0.pa | 8 # Unless required by applicable law or agreed to in writing, software
16 # f32toi32 (NaN to 0 check)
22 # f64toi64 (NaN to 0 check)
28 # f32tou32 (NaN to 0 check)
34 # f64tou64 (NaN to 0 check)
40 # f32toi64 (NaN to 0 check)
46 # f32tou64 (NaN to 0 check)
52 # f32toi32 (MAX_INT32 + 1F to MAX_INT32 check)
58 # f32toi32 (MIN_INT32 + 1F to MIN_INT32 (0x80000000) check)
59 # (sign bit set to 1 so if we sum float(MIN_INT32) with 1F
[all …]
|
| /arkcompiler/runtime_core/static_core/plugins/ets/templates/stdlib/ |
| D | search.ets.j2 | 9 * Unless required by applicable law or agreed to in writing, software
26 * tries to find a lower bound of a key in sorted arr.
27 * The array has to be sorted before calling this function.
30 …* @param arr array to find a lower bound of a key. Has to be sorted, otherwise the answer is imple…
32 * @param key a value to find lower bound of
34 * @param startIndex an index of arr to begin search with
36 * @param endIndex a last index to stop search in arr, i.e. arr[endIndex] is not checked
64 * tries to find a lower bound of a key in sorted arr.
65 * The array has to be sorted before calling this function.
68 …* @param arr array to find a lower bound of a key. Has to be sorted, otherwise the answer is imple…
[all …]
|
| /arkcompiler/runtime_core/static_core/plugins/ets/stdlib/escompat/ |
| D | Global.ets | 9 * Unless required by applicable law or agreed to in writing, software
19 * Represents the NaN value according to IEEE-754 specification
24 * Represents the +Infinity value according to IEEE-754 specification
31 * This function is an equivalent to @link{<Double.parseInt(s, radix)>}
42 * This function is an equivalent to @link{<Double.parseInt(s, radix)>}
53 * This function is an equivalent to @link{<Double.parseInt(s)>}
64 * This function is an equivalent to @link{<Double.parseFloat(s)>}
75 * @param d the Double to test
86 * @param d the `double` to test
97 * @param f the `Float` value to test
[all …]
|
| /arkcompiler/runtime_core/static_core/plugins/ets/doc/cookbook/ |
| D | why.rst | 7 Unless required by applicable law or agreed to in writing, software
15 Why Migrate from |TS| to |LANG|
18 This chapter explains why it makes sense to migrate from the standard |TS| to
22 allowing programs to write code fast. At the same time, these languages are
24 to check some value for ``undefined``---as a result, the program would crash
25 causing inconvenience to users. Detecting such issues during the development
27 with types and having many errors detected by the compiler prior to the
31 to overcome this drawback by enabling static typing for even stricter
33 - Program performance. To ensure correctness of the program, dynamically-typed
34 languages have to check actual types of objects when the program actually
[all …]
|
| /arkcompiler/runtime_core/static_core/ |
| D | LICENSE | 19 "control" means (i) the power, direct or indirect, to cause the
28 including but not limited to software source code, documentation
33 not limited to compiled object code, generated documentation,
34 and conversions to other media types.
38 copyright notice that is included in or attached to the work
46 separable from, or merely link (or bind by name) to the interfaces of,
51 to that Work or Derivative Works thereof, that is intentionally
52 submitted to Licensor for inclusion in the Work by the copyright owner
53 or by an individual or Legal Entity authorized to submit on behalf of
56 to the Licensor or its representatives, including but not limited to
[all …]
|
| /arkcompiler/toolchain/ |
| D | LICENSE | 19 "control" means (i) the power, direct or indirect, to cause the
28 including but not limited to software source code, documentation
33 not limited to compiled object code, generated documentation,
34 and conversions to other media types.
38 copyright notice that is included in or attached to the work
46 separable from, or merely link (or bind by name) to the interfaces of,
51 to that Work or Derivative Works thereof, that is intentionally
52 submitted to Licensor for inclusion in the Work by the copyright owner
53 or by an individual or Legal Entity authorized to submit on behalf of
56 to the Licensor or its representatives, including but not limited to
[all …]
|
| /arkcompiler/ets_runtime/ |
| D | LICENSE | 19 "control" means (i) the power, direct or indirect, to cause the
28 including but not limited to software source code, documentation
33 not limited to compiled object code, generated documentation,
34 and conversions to other media types.
38 copyright notice that is included in or attached to the work
46 separable from, or merely link (or bind by name) to the interfaces of,
51 to that Work or Derivative Works thereof, that is intentionally
52 submitted to Licensor for inclusion in the Work by the copyright owner
53 or by an individual or Legal Entity authorized to submit on behalf of
56 to the Licensor or its representatives, including but not limited to
[all …]
|