Search results
Results from the WOW.Com Content Network
Like many other P-code machines, the UCSD P-Machine is a stack machine, which means that most instructions take their operands from a stack, and place results back on the stack. Thus, the add instruction replaces the two topmost elements of the stack with their sum. A few instructions take an immediate argument.
Bytecode (also called portable code or p-code) is a form of instruction set designed for efficient execution by a software interpreter.Unlike human-readable [1] source code, bytecodes are compact numeric codes, constants, and references (normally numeric addresses) that encode the result of compiler parsing and performing semantic analysis of things like type, scope, and nesting depths of ...
This performance advantage was eroded by the later availability of p-code to native machine code translators, and mainstream 16-bit microprocessors such as the Intel 8086 and Motorola 68000. When details of the MicroEngine were first released, the system accumulated a very large number of pre-orders (for the time).
P-code is an alternative term for bytecode, machine-independent code that achieves independence by targeting a p-code machine, a virtual machine designed for running p-code rather than the intention to emulate any specific hardware architecture.
Joel McCormack is an American computer scientist who designed the NCR Corporation version of the p-code machine, which is a kind of stack machine popular in the 1970s as the preferred way to implement new computing architectures and languages such as Pascal and BCPL.
Machine code is generally different from bytecode (also known as p-code), which is either executed by an interpreter or itself compiled into machine code for faster (direct) execution. An exception is when a processor is designed to use a particular bytecode directly as its machine code, such as is the case with Java processors .
A revision of the p-code engine (i.e., the p-Machine) meant a change to the p-code language, and therefore compiled code is not portable between different p-Machine versions. Each revision was represented with a leading Roman Numeral, while operating system revisions were enumerated as the "dot" number following the p-code Roman Numeral.
The default OperandSize and AddressSize to use for each instruction is given by the D bit of the segment descriptor of the current code segment - D=0 makes both 16-bit, D=1 makes both 32-bit. Additionally, they can be overridden on a per-instruction basis with two new instruction prefixes that were introduced in the 80386: