| /arkcompiler/runtime_core/docs/ |
| D | assembly_format.md | 5 …e format for Panda platform. Assembly files are human-readable and human-writeable plain text file…
19 Comments are marked with the `#` character. All characters that follow it (including the `#` charac…
25 Following numeric literals are supported:
27 …integers not larger than 64 bits. Hexadecimal literals are prefixed with `0x`. Binary literals are…
28 …resented with IEEE 754. Hexadecimal floating-point literals are prefixed with `0x`. They are first…
48 A simple identifier is a sequence of ASCII characters. Allowed characters in the sequence are:
58 * All identifiers are case sensitive.
70 …support many of them. To deal with language-specific metadata, annotations are used, defined as fo…
76 Values are optional. In such case, only `key` is needed.
81 * All keys are unique within a single annotation list.
[all …]
|
| D | ir_format.md | 13 …f execution of optimizations and analyses is very important. Firstly there are dependencies betwee…
45 The benefits of some optimizations are not obvious or do need profiling information to implement th…
76 …zations. For this, need to support ARMv8-M Instruction Set(only those instructions that are needed)
81 …de is converted to high level instruction and architecturally independent optimizations are made.
87 … is considered to be the average number of 'native' instructions(ARM) that are spent compiling a s…
112 * Information about the method for which transformations are made
124 * A double-linked list of instructions, which are contained in the block
146 …h an empty block when there are `Phi` instructions in block 2 with different inputs from those inc…
176 Instructions are implemented by class inheritance.
192 …nt instruction. It contains a constant and type of the constant. Constants are contained only in s…
[all …]
|
| D | rationale-for-bytecode.md | 17 operands are _stack operands_ that reside in a special data structure called _stack_. The program
37 In case there is a chance for ambiguity, the terms "virtual registers" and "virtual stack" are used
47 In _stack-based_ approach, operands are implicitly encoded in the operation, which results in
60 In _register-based approach_, operands are explicitly encoded in the operation, which results in
89 However, to address the issue of compactness, two main tweaks are used:
92 * Variable size of instructions with frequent instructions are encoded to be smaller.
110 With this approach, we are no longer required to encode destination register, it is "hardcoded" to
118 are popular) and for increment/decrement instructions (when loop variable is only read in a loop
179 overloads are calls (different number of operands) and calls are the most popular instructions in
185 `adda ...` instruction, what are types of its operands?
[all …]
|
| D | doxygen.config | 30 # double-quotes, unless you are using Doxywizard) that should identify the
84 # Possible values are: Afrikaans, Arabic, Armenian, Brazilian, Catalan, Chinese,
97 # descriptions after the members that are listed in the file and class
106 # Note: If both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
117 # following values are used ($name is automatically replaced with the name of
133 # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
171 # specify the list of include paths that are normally passed to the compiler
206 # Note that setting this tag to YES also means that rational rose comments are
251 # instance, some of the names that are used will be different. The list of all
292 # the files are not read by doxygen.
[all …]
|
| D | design-of-interpreter.md | 40 1. Bytecode is register-based: all arguments and variables are mapped to virtual registers,
84 1. All metadata entities are split into two groups: local (declared in the current executable file)
87 more efficient data reads from the Panda binary file. Foreign entities are loaded from their
126 are reimplemented by the platform.
132 1. Interpreters are by nature slower than native code execution. Slowdown can be explained by:
167 1. All virtual registers are "tagged", meaning that they contain both the payload and additional
185 size of the payload we are required to store in a virtual register). The second 64 is for tag
210 are small chunks of hand-written Panda Assembly covering corner cases, while the majority of
211 cases are covered by automatically generated chunks.
218 Lots of things are being created in parallel, and currently there is no stable front-end for Panda
|
| D | aot.md | 29 To access to the `.text` and `.aot` sections from AOT loader following symbols are defined:
46 Classes and methods are uniquely identified (inside one file) by their panda file id (`panda_file::…
104 to cache pointers which are recieved from runtime calls - PLT resolvers. They are described in a se…
122 - `--location` - path where panda files are actually stored in the device
125 Paoc uses Panda runtime inside, thus, runtime's options are also may be specified. If paoc is ran n…
171 Disassembler creates files with following name format `disasm-<METHOD_NAME>.txt`. IR dumps are writ…
174 to dump ir only after last (codegen) pass. All of these options are used at compile time.
|
| D | cfi_directives.md | 30 … saved `callees` from stack and also `fp`/`lr`. Here we annotate that saved registers are restored.
34 There are bridges which `hack` stack memory (setting `stack pointer` to other stack frame), i.e.:
41 In that case we "say" to `debugger` that we are not going to return to previous frame. So we direct…
|
| /arkcompiler/ets_frontend/arkguard/ |
| D | README.md | 17 global names obfuscation and property names obfuscation are disabled by default, as they may
18 cause runtime error if they are enabled by default.
54 When you are building HAP or HAR, the final obfucation rules are combination of self's `ruleOptions…
56 If you are building HAR, the content of `obfuscation.txt` is the combination of self's `consumerFil…
57 dependent libraries' `consumerFiles` properties and dependent HAR's `obfuscation.txt`. If you are b…
63 The files `obfuscation-rules.txt` and `consumer-rules.txt` are created by DevEco Studio automatical…
117 * the property names that are specified by [keep options](#keep-options).
119 * the property names that are string literals. For example, the property names "name" and "age" in …
129 …Note: If there are string literal property names which contain special characters (that is, all ch…
137 * the global names that are not declared in the current file.
[all …]
|
| /arkcompiler/runtime_core/compiler/docs/ |
| D | paoc.md | 4 There are three [modes](#--paoc-mode) of `paoc`:
6 …ample, to get `--compiler-dump` or to ensure that all of the compiler passes are applied correctly.
20 - A boolean option that allows to continue the compilation if some of the methods are failed to com…
59 If none of them are specified, `paoc` will compile every method from [--paoc-panda-files](#`--paoc-…
87 # Keys are functions' full names (i.e. `class::method`).
88 … # Values are arrays whose elements should be a name of a cluster or it's index (starting from 0).
89 # If some of the options are intersecting, the last (in the array) would be applied.
99 # Keys are clusters' names.
100 # Values are objects with `"option": argument` elements.
|
| D | reg_alloc_graph_coloring_doc.md | 18 …Chordal graph is that: its max-clique value equals to Chromatic one; there are exist Perfect Elimi…
20 …are collected from Architecture and remapped (to sequential numbering) in order <caller-saved, cal…
27 …ity edges represent move-relation between values. Currently affinity edges are added for inputs of…
32 …tart another one. This way we don’t have situations when different cliques are colored in parallel…
36 There are two classes of approaches for coalescing, that is:
38 - Biasing, is a way when in front of coloring nodes are “hinted” with preferred colors. And on stag…
42 …orithm which is recursive call to DFS, until all nodes having affine edges are visited. Marker of …
43 Biases are collected to array of tuples <bias color, call-sites count>, where color value initially…
47 …and neighbor bias-colors (if any). To account this information two bit-sets are used respectively.
55 …sponding interval is performed. All nodes at the moment are assigned by colors, these colors are r…
[all …]
|
| D | aot_cha.md | 8 result the order of files in class path and files themselves are enough to verify the class context…
37 The wrong usage. Some classes were omitted during AOT compilation due to the fact that they are not…
61 is performed during Runtime initialization when only boot panda files are loaded. The verification …
65 …ing their paths on the target. `--paoc-boot-location` specifies the path where boot panda files are
68 …-panda-files must match between `ark_aot` and `ark`. It means, that if you are compiling an AOT fi…
91 …odPtr is needed only to obtain the virtual table index. The indices inside virtual tables are still
|
| D | aot_resolve_string.md | 26 There are two options controlling when and how many string will be saved into PLT-slots:
47 …stored inside PLT-slots have to be treated as GC-roots to prevent its scavenge in case there are no
52 …ung GC, but it also requires update during update phase. As yet another optimization PLT-slots are
53 updated only if `StringTable` was updated during GC, because both these structures are referencing …
|
| D | plt.md | 23 consecutive slots are reserved in PLT-GOT table. `FirstSlot` is filled during AOT file creation and…
30 parameters are already in proper registers):
67 slots are reserved in PLT-GOT table. `FirstSlot` is filled during AOT file creation and contains `m…
117 three consecutive slots are reserved in PLT-GOT table. `FirstSlot` is filled during AOT file creati…
118 `SecondSlot` and `ThirdSlot` are filled with zeroes and after resolving they both store `Class poin…
168 …n platform-independent file `code_generator/target/target.cpp`, although there are actually several
185 …olvers (all but CallStatic) "return address" and "previous frame" values which are already on stack
190 registers are saved directly into appropriate places in previous CFrame.
202 This step is done using `MakeCallAot` function with properly calculated offset. Resolvers are place…
217 Registers are loaded in the same manner they were saved. So, in CallStatic we have to adjust stack …
|
| D | try_catch_blocks_ir.md | 64 `Try-begin` and `Try-end` - are try boundaries basic blocks. Both of them have one normal control-f…
66 Edges form `Try-end` block to the catch-handlers are needed for correct linear order of basic block…
125 …s virtual register and its inputs are values of these virtual registers in the points where throwa…
148 - vector of try-begin blocks in order they are declared in the bytecode;
|
| /arkcompiler/runtime_core/tests/cts-generator/cts-template/ |
| D | isinstance.yaml | 54 …type in type hierarchy or T is such array that O array elements are the same or subtype of T array…
331 …type in type hierarchy or T is such array that O array elements are the same or subtype of T array…
347 # O and T are of the same type, std object
353 # O and T are of the same type, custom object
359 # O and T are of the same type, string
364 # O and T are of the same type, type
393 # O and T are of the same type, both arrays, std object
401 # O and T are of the same type, both arrays, custom object
409 # O and T are of the same type, both arrays, string
456 …type in type hierarchy or T is such array that O array elements are the same or subtype of T array…
[all …]
|
| /arkcompiler/ets_runtime/ecmascript/compiler/ |
| D | circuit_ir_specification.md | 5 …en.wikipedia.org/wiki/Logic_gate) are nodes, wires are directed edges. For every gate, inputs are …
9 …are named **state gates** (since they acted like a [finite state machine](https://en.wikipedia.org…
11 …are named **computation gates**. A computation gate can do simple things such as adding two intege…
13 …are [linearly ordered](https://en.wikipedia.org/wiki/Total_order). However, in Circuit IR, computa…
17 …are **[selector](https://en.wikipedia.org/wiki/Multiplexer) gates** such as `VALUE_SELECTOR` and `…
19 …lem, **[relay](https://en.wikipedia.org/wiki/Relay) gates** `DEPEND_RELAY` are introduced. They ta…
23 …are several nodes named **root nodes** in Circuit IR. They are not called "gates" since they do no…
33 …IST`: Registering all value origins such as constants and arguments. (they are special computation…
35 The offsets of root nodes are fixed, so they can be accessed instantly via `GateRef Circuit::GetRoo…
41 There are two levels of types of values in Circuit IR:
[all …]
|
| /arkcompiler/runtime_core/docs/bc_verification/ |
| D | types_n_values.md | 3 Types are divided into next kinds:
8 3. Physycal (concrete) types. They are parameterized types by abstract and storage types.
12 Types are formed by some `Sort`, an uniq identifier of the type family, and particular parameters.
24 - Sorts are denoted by some `Literals`. Where `Literal` is a word composed of characters from set `…
26 - Types are denoted by sort literal and parameters in parenthesis. For instance: `Array(~i8())`.
27 - Type parameters are just types prepended by variance sign, `-` - contrvariant, `+` - variant, `~`…
80 Types which are in circular subtyping relation, like `A <: B <: C <: A`, are indistinguishable
|
| D | type_system.md | 3 Type system is simple: there are only parametric type families, named as `Sort`s, and their instanc…
5 For simplicity, all literals without parens are Sorts, with parens - Types.
20 Internally they are just indices.
26 Variances are:
60 Loops in subtyping relation are threated as classes of equivalence, for instance:
|
| D | cflow_checks.md | 39 ## Cflow transitions, which are subjects for checks
78 Mis-jumps, or improper termination of cflow at the end of the body are prohibited.
101 Conditional jumps are in grey zone, if they may be proven as always jump
103 of verifier, conditional jumps at the end of the method are prohibited.
145 fallthrough on beginning of exception handler are allowed.
291 By default such cflow transitions are prohibited.
313 By default such jumps are prohibited currently.
|
| /arkcompiler/ets_runtime/test/perform/string/ |
| D | string.js | 30 const str = 'Apples are round, and apples are juicy.';
54 const str = "Hello World. How are you doing?"
123 const str = "Hello World. How are you doing?"
145 const str = "Hello World. How are you doing?"
156 const str = "Hello World. How are you doing?"
178 const str = "Hello World. How are you doing?"
189 const str = "Hello World. How are you doing?"
196 print("string substr the two parameters are adjacent numbers : " + time3);
288 const str = "Hello World. How are you doing?"
321 const str = "Hello World. How are you doing?"
[all …]
|
| /arkcompiler/ets_runtime/test/typeinfer/automatedcases/ |
| D | genericCallWithOverloadedFunctionTypedArguments.ts | 22 // Inferences are made quadratic-pairwise to and from these overload sets
46 …let r5 = foo5(x => x); // any => string (+1 overload) [inferences are made for T, but lambda not c…
55 …let r8 = foo6(x => x); // any => string (+1 overload) [inferences are made for T, but lambda not c…
64 …let r12 = foo7(1, (x) => x); // any => string (+1 overload) [inferences are made for T, but lambda…
65 …let r13 = foo7(1, <T>(x: T) => ''); // any => string (+1 overload) [inferences are made for T, but…
67 …let r14 = foo7(1, a); // any => string (+1 overload) [inferences are made for T, but lambda not co…
|
| /arkcompiler/runtime_core/bytecode_optimizer/ |
| D | reg_encoder.h | 33 * * locals (>= 0) are registers allocated for function's local variables;
34 * * temps (>= 0) are temporary registers that can be allocated by spill-fill
36 * * arguments (>= 0) are registers allocated for function's arguemnts.
40 * Locals and temps are allocated densely: if there are more than 0 locals
58 * actual inputs r16+. If such instructions are found, some lower registers
59 * (starting with r0, but no more than MAX_NUM_INPUTS registers) are reserved as
60 * temps and corresponding spills are emitted where needed. After this is done,
|
| /arkcompiler/ets_frontend/ts2panda/scripts/ |
| D | diagnosticMessages.json | 94 "A 'with' statements are not allowed in strict mode.": {
150 "Octal literals are not allowed in strict mode.": {
154 "Octal escape sequences are not allowed in strict mode.": {
250 "Decorators are not valid here.": {
258 "Invalid use of '{0}'. Class definitions are automatically in strict mode.": {
270 …"Identifier expected. '{0}' is a reserved word in strict mode. Class definitions are automatically…
274 …"Identifier expected. '{0}' is a reserved word in strict mode. Modules are automatically in strict…
310 …"Function declarations are not allowed inside blocks in strict mode when targeting 'ES3' or 'ES5'.…
314 …"Function declarations are not allowed inside blocks in strict mode when targeting 'ES3' or 'ES5'.…
318 …"Function declarations are not allowed inside blocks in strict mode when targeting 'ES3' or 'ES5'.…
[all …]
|
| /arkcompiler/runtime_core/isa/ |
| D | asserts.rb | 39 assert('Non-prefixed instruction opcode indexes are sorted') do
43 assert('Prefix opcode indexes are sorted') do
79 assert('All tags are unique between categories') do
83 assert('All tags are used') do
91 assert('All tags are defined') do
99 assert('Format operands are parseable') { Panda.instructions.each(&:operands) }
101 assert('Verification, exceptions and properties are not empty for every instruction group') do
|
| /arkcompiler/toolchain/build/toolchain/ |
| D | toolchain.gni | 27 # with the build. Used on iOS to ship official builds (as they are built
42 # Clang compiler version. Clang files are placed at version-dependent paths.
77 # While other "tool"s in a toolchain are specific to the target of that
78 # toolchain, the "stamp" and "copy" tools are really generic to the host;
|