2019
DOI: 10.1007/978-3-030-37487-7_1
|View full text |Cite
|
Sign up to set email alerts
|

Rapid Instruction Decoding for IA-32

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
4
0

Year Published

2020
2020
2023
2023

Publication Types

Select...
1
1

Relationship

0
2

Authors

Journals

citations
Cited by 2 publications
(5 citation statements)
references
References 1 publication
0
4
0
Order By: Relevance
“…Since we are concerned with automatically generated decoders, we will not consider manual decoders [9,10,18] that are traditionally implemented as nested conditionals. Nor will we deal with decoder generators that require human intervention or data-mining in pregrouping the instructions or providing extra semantic information [11][12][13]17].…”
Section: Functional Analysis Of Decoder Decision Tree Algorithmsmentioning
confidence: 99%
“…Since we are concerned with automatically generated decoders, we will not consider manual decoders [9,10,18] that are traditionally implemented as nested conditionals. Nor will we deal with decoder generators that require human intervention or data-mining in pregrouping the instructions or providing extra semantic information [11][12][13]17].…”
Section: Functional Analysis Of Decoder Decision Tree Algorithmsmentioning
confidence: 99%
“…The opcode is a bytecode-level representation of the instruction, that identifies it for the CPU (as well as for our emulator) and thus must also be used as a part of the code generation. This is known as "instruction decoding" [Kli19b]. "Inlining" is the name we use to refer to the "true" compilation where an input instruction is compiled to one or more individual atomic bytecode instructions of the target platform.…”
Section: Main Challenges and Approachesmentioning
confidence: 99%
“…Determining which instruction to execute next ("instruction decoding" [Kli19b]), in a broad sense, is just parsing [ZB14]. Having the knowledge about the general syntactic structure of each instruction (its length in bytes, positions of instructiondefining opcode bytes and their values) makes this a trivial generative task, with some handling of corner cases-e.g., the EXECUTE instruction mentioned above, does not return to the original call location if the executed instruction is a branching one.…”
Section: Semantic Steps Modellingmentioning
confidence: 99%
See 2 more Smart Citations