Java Bytecode: Difference between revisions
Jump to navigation
Jump to search
(Created page with "
A Java Bytecode is a Java Virtual Machine that ...
* <B>See:</B> Java Virtual Machine, Bytecode, Opcode, Sun Microsystems, Java Platform.
----
...") |
No edit summary |
||
| Line 1: | Line 1: | ||
A [[Java Bytecode]] is an [[internal representation language]] for a [[Java Virtual Machine]]. | |||
A [[Java Bytecode]] is a [[Java Virtual Machine]] | * <B>See:</B> [[Bytecode]], [[Opcode]], [[Java Platform]], [[JVM Programming Language]]. | ||
* <B>See:</B> | |||
---- | ---- | ||
---- | ---- | ||
| Line 10: | Line 9: | ||
** '''Java bytecode''' is the form of instructions that the [[Java virtual machine]] executes. Each [[bytecode]] [[opcode]] is one byte in length, although some require parameters, resulting in some multi-byte instructions. Not all of the possible 256 [[opcode]]s are used. 51 are reserved for future use. Beyond that, [[Sun Microsystems]], the original developer of the [[Java platform]], had set aside three values to be permanently unimplemented.<ref name="reserved_opcodes">[http://docs.oracle.com/javase/specs/jvms/se7/html/jvms-6.html#jvms-6.2 VM Spec - Reserved Opcodes] </ref> | ** '''Java bytecode''' is the form of instructions that the [[Java virtual machine]] executes. Each [[bytecode]] [[opcode]] is one byte in length, although some require parameters, resulting in some multi-byte instructions. Not all of the possible 256 [[opcode]]s are used. 51 are reserved for future use. Beyond that, [[Sun Microsystems]], the original developer of the [[Java platform]], had set aside three values to be permanently unimplemented.<ref name="reserved_opcodes">[http://docs.oracle.com/javase/specs/jvms/se7/html/jvms-6.html#jvms-6.2 VM Spec - Reserved Opcodes] </ref> | ||
<references/> | <references/> | ||
<BR> | |||
* ([[2013_IntermediateRepresentation|Chow, 2013]]) ⇒ [[author::Fred Chow]]. ([[year::2013]]). "[http://queue.acm.org/detail.cfm?id=2544374 Intermediate Representation]." In: [[Queue Journal]], 11(10). [http://dx.doi.org/10.1145/2542661.2544374 doi:10.1145/2542661.2544374] | |||
** QUOTE: [[Java bytecode]] is the first example of an [[IR Language|IR]] with an [[open standard definition]] that is independent of [[compiler]]s, because [[JVM]] is so widely accepted that it has spawned numerous [[compiler]] and [[VM implementation]]s. The prevalence of [[JVM]] has led to many other [[programming language|language]]s being translated to [[Java bytecode]],<ref>[[JVM language]]s; http://en.wikipedia.org/wiki/List_of_JVM_languages.</ref> but because it was originally defined to serve only the [[Java language]], support for [[high-level abstraction]]s not present in [[Java]] is either not straightforward or absent. This lack of generality limits the use of [[Java bytecode]] as a universal [[IR Language|IR]]. | |||
---- | ---- | ||
[[Category:Concept]] | [[Category:Concept]] | ||
__NOTOC__ | __NOTOC__ | ||
Revision as of 19:47, 13 December 2013
A Java Bytecode is an internal representation language for a Java Virtual Machine.
References
2013
- (Wikipedia, 2013) ⇒ http://en.wikipedia.org/wiki/java_bytecode Retrieved:2013-12-13.
- Java bytecode is the form of instructions that the Java virtual machine executes. Each bytecode opcode is one byte in length, although some require parameters, resulting in some multi-byte instructions. Not all of the possible 256 opcodes are used. 51 are reserved for future use. Beyond that, Sun Microsystems, the original developer of the Java platform, had set aside three values to be permanently unimplemented.[1]
- (Chow, 2013) ⇒ Fred Chow. (2013). "Intermediate Representation." In: Queue Journal, 11(10). doi:10.1145/2542661.2544374
- QUOTE: Java bytecode is the first example of an IR with an open standard definition that is independent of compilers, because JVM is so widely accepted that it has spawned numerous compiler and VM implementations. The prevalence of JVM has led to many other languages being translated to Java bytecode,[1] but because it was originally defined to serve only the Java language, support for high-level abstractions not present in Java is either not straightforward or absent. This lack of generality limits the use of Java bytecode as a universal IR.