Java bytecode: Difference between revisions

Revision as of 06:53, 17 June 2017

Revision as of 18:21, 24 August 2025

(88 intermediate revisions by 69 users not shown)

Line 1:

{{Short description|Instruction set of the Java virtual machine}}

'''Java bytecode''' is the [[instruction set]] of the [[Java virtual machine]] (JVM). Each [[bytecode]] is composed of one, or in some cases two bytes that represent the instruction ([[opcode]]), along with zero or more bytes for passing parameters.

{{Use dmy dates|date=November 2023}}

{{Use American English|date=November 2023}}

'''Java bytecode''' is the instruction set of the [[Java virtual machine]] (JVM), the language to which [[Java (programming language)|Java]] and other JVM-compatible [[source code]] is [[compiler|compiled]].<ref name="oracle jvm spec">{{Cite web|url=http://docs.oracle.com/javase/specs/jvms/se8/html/|title=Java Virtual Machine Specification|publisher=Oracle|access-date=14 November 2023}}</ref> Each instruction is represented by a single [[byte]], hence the name [[bytecode]], making it a compact form of [[data]].<ref name="JVM Book">{{Cite book|last=Lindholm|first=Tim|title=The Java Virtual Machine Specification|year=2015|publisher=Oracle|isbn=978-0133905908}}</ref>

For example,

"Dhurr wara", "Suppli nischit", etc.

Due to the nature of bytecode, a Java bytecode [[computer program|program]] is runnable on any machine with a compatible JVM, without the lengthy process of compiling from source code.

Of the 256 possible byte-long [[opcode]]s, {{as of|2015|lc=y}}, 198 are in use (~78%), 54 are reserved for future use (~21%), and 3 instructions (~1%) are set aside as 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 used at [[Runtime (program lifecycle phase)|runtime]] either [[interpreter (computing)|interpreted]] by a JVM or compiled to machine code via [[Just-in-time compilation|just-in-time]] (JIT) compilation and run as a native application.

The Java bytecode system does not directly support floating point operations beyond 32 bits, except indirectly via bytecodes that enable use of 64-bit and 80-bit intermediate IEEE floating point operations.

{{Citation needed|reason=seems to contradict the following sentence|date=May 2017}}

As Java bytecode is designed for a cross-platform compatibility and security, a Java bytecode application tends to run consistently across various [[computer hardware|hardware]] and [[software]] configurations.<ref>{{Cite journal|last=Arnold|first=Ken|title=The Java Programming Language|journal=Sun Microsystems|year=1996|volume=1|issue=1|pages=30–40}}</ref>

The Java bytecode system directly supports 32-bit and 64-bit floating point operations (IEEE single-precision and IEEE double-precision).<ref>

Tim Lindholm; Frank Yellin; Gilad Bracha; Alex Buckley.

[http://docs.oracle.com/javase/specs/jvms/se7/html/jvms-2.html#jvms-2.11.1 "The Structure of the Java Virtual Machine"].

2013.

</ref>

== Relation to Java ==

AIn [[Javageneral, (programminga language)|Java [[programmer]] programmer does not need to beunderstand awareJava ofbytecode or understandeven Javabe bytecodeaware atof allit. However, as suggested in the [[IBM]] developerWorks journal, "Understanding bytecode and what bytecode is likely to be generated by a [[Java compiler]] helps the Java programmer in the same way that knowledge of [[assembly language|assembly]] helps the [[C (programming language)|C]] or [[C++]] programmer."<ref>[http{{Cite web |title=IBM Developer |url=https://wwwdeveloper.ibm.com/developerworkslanguages/ibmjava/library/it |access-haggar_bytecode/date=20 UnderstandingFebruary bytecode2006 makes you a better programmer]|website=developer.ibm.com}}</ref>

== Instruction set architecture ==

The bytecode comprises various instruction types, including data manipulation, control transfer, object creation and manipulation, and method invocation, all integral to Java's object-oriented programming model.<ref name="oracle jvm spec"/>

The JVM is both a [[stack machine]] and a [[register machine]]. Each [[Call stack#STACK-FRAME|frame]] for a method call has an "operand stack" and an array of "local variables".<ref name="jvm">{{cite book |last1=Lindholm |first1=Tim |last2=Yellin |first2=Frank |last3=Bracha |first3=Gilad |last4=Buckley |first4=Alex |title=The Java Virtual Machine Specification |edition=Java SE 8 |date=2015-02-13 |url=http://docs.oracle.com/javase/specs/jvms/se8/html/}}</ref>{{rp|2.6}} <ref name="JVM Book"/> The operand stack is used for passing operands to computations and for receiving the return value of a called method, while local variables serve the same purpose as [[Processor register|registers]] and are also used to pass method arguments. The maximum size of the operand stack and local variable array, computed by the compiler, is part of the attributes of each method.<ref name="jvm"/>{{rp|4.7.3}} Each can be independently sized from 0 to 65535 values, where each value is 32 bits. {{code|lang="java"|long}} and {{code|lang="java"|double}} types, which are 64 bits, take up two consecutive local variables<ref name="jvm"/>{{rp|2.6.1}} (which need not be 64-bit aligned in the local variables array) or one value in the operand stack (but are counted as two units in the depth of the stack).<ref name="jvm"/>{{rp|2.6.2}}

=== Instruction set ===

{{further|List of Java bytecode instructions}}

Each [[bytecode]] is composed of one byte that represents the [[opcode]], along with zero or more bytes for operands.<ref name="jvm"/>{{rp|2.11}}

Of the 256 possible byte-long [[opcode]]s, {{as of|2015|lc=y}}, 202 are in use (~79%), 51 are reserved for future use (~20%), and 3 instructions (~1%) are permanently reserved for JVM implementations to use.<ref name="jvm"/>{{rp|6.2}} Two of these (<code>impdep1</code> and <code>impdep2</code>) are to provide traps for implementation-specific software and hardware, respectively. The third is used for debuggers to implement breakpoints.

Instructions fall into a number of broad groups:

* Load and store (e.g. <code>aload_0</code>, <code>istore</code>)

* Arithmetic and logic (e.g. <code>ladd</code>, <code>fcmpl</code>)

* Type conversion (e.g. <code>i2b</code>, <code>d2i</code>)

* Object creation and manipulation (<code>new</code>, <code>putfield</code>)

* Operand stack management (e.g. <code>swap</code>, <code>dup2</code>)

* Control transfer (e.g. <code>ifeq</code>, <code>goto</code>)

* Method invocation and return (e.g. <code>invokespecial</code>, <code>areturn</code>)

There are also a few instructions for a number of more specialized tasks such as exception throwing, synchronization, etc.

Many instructions have [[Opcode prefix|prefixes]] and/or suffixes referring to the types of operands they operate on.<ref name="jvm"/>{{rp|2.11.1}} These are as follows:

{| class="wikitable"

|-

! Prefix-/suffix !! Operand type

|-

| <code>i</code> || integer

Line 48 ⟶ 58:

|-

| <code>d</code> || double

|-

| <code>z</code> || boolean

|-

| <code>a</code> || reference

|}

For example, "<code>iadd"</code> will add two integers, while "<code>dadd"</code> will add two doubles. The "<code>const"</code>, "<code>load"</code>, and "<code>store"</code> instructions may also take a suffix of the form "<code>_''n''"</code>, where ''n'' is a number from 0–3 for "<code>load"</code> and "<code>store"</code>. The maximum ''n'' for "<code>const"</code> differs by type.

The "<code>const"</code> instructions push a value of the specified type onto the stack. For example, "<code>iconst_5"</code> will push an integer (32 bit value) with the value 5{{clarify|date=August 2016}}onto the stack, while "<code>dconst_1"</code> will push a double (64 bit floating point value) with the value 1 onto the stack. There is also an "<code>aconst_null"</code>, which pushes "a {{code|lang=java|null"}} reference. The ''n'' for the "<code>load"</code> and "<code>store"</code> instructions specifies the ___locationindex in the local variable table{{clarify|date=October 2010}}array to load from or store to. The "<code>aload_0"</code> instruction pushes the object in local variable 0 onto the stack (this is usually the "<code>[[this" (computer programming)|this]]</code> object). "<code>istore_1"</code> stores the integer on the top of the stack into local variable 1. For variableslocal withvariables higherbeyond numbers3 the suffix is dropped and operands must be used.

== Example ==

Line 62 ⟶ 70:

Consider the following Java code:

<sourcesyntaxhighlight lang="java">

outer:

for (int i = 2; i < 1000; i++) {

Line 69 ⟶ 77:

continue outer;

}

System.out.println (i);

}

</syntaxhighlight>

</source>

A Java compiler might translate the Java code above into byte codebytecode as follows, assuming the above was put in a method:

<sourcesyntaxhighlight lang="jasmin">

0: iconst_2

1: istore_1

Line 97 ⟶ 105:

38: iinc 1, 1

41: goto 2

44: return</sourcesyntaxhighlight>

== Generation ==

{{Further information|List of JVM languages}}

The most common language targeting [[Java virtual machine]] by producing Java bytecode is Java. Originally only one compiler existed, the [[javac]] compiler from [[Sun Microsystems]], which compiles [[Java source code]] to Java bytecode; but because all the specifications for Java bytecode are now available, other parties have supplied compilers that produce Java bytecode. Examples of other compilers include:

*Eclipse compiler for Java (ECJ)

*[[Jikes]], compiles from Java to Java bytecode (developed by [[IBM]], implemented in [[C++]])

*Espresso, compiles from Java to Java bytecode (Java 1.0 only)

*[[GNU Compiler for Java]] (GCJ), compiles from Java to Java bytecode; it can also compile to native [[machine code]] and iswas part of the [[GNU Compiler Collection]] (GCC) up until version 6.

Some projects provide Java assemblers to enable writing Java bytecode by hand. Assembly code may be also generated by machine, for example by a compiler targeting a [[Java virtual machine]]. Notable Java assemblers include:

*[[Jasmin (Java assembler)|Jasmin]], takes text descriptions for Java classes, written in a simple assembly-like syntax using Java virtual machine instruction set and generates a Java class file<ref>[http{{Cite web|url=https://jasmin.sourceforge.net /|title=Jasmin homeHome page<!-- BotPage|website=jasmin.sourceforge.net|accessdate=2 generated titleJune -->]2024}}</ref>

*Jamaica, a [[Macro (computer science)|macro]] [[assembly language]] for the [[Java virtual machine]]. Java syntax is used for class or interface definition. Method bodies are specified using bytecode instructions.<ref>[http{{Cite web|url=https://www.judoscriptjavaworld.orgcom/jamaicaarticle/2072355/core-java/learn-to-speak-jamaican.html |title=Jamaica: The Java virtual machine (JVM) macro assembler<!-- Bot generated title -->]|archive-url=https://web.archive.org/web/20231114000632/https://www.infoworld.com/article/2072355/learn-to-speak-jamaican.html|archive-date=14 November 2023|work=JavaWorld |accessdate=2 June 2024 |last1=Huang |first1=James Jianbo }}</ref>

*Krakatau Bytecode Tools, currently contains three tools: a decompiler and disassembler for Java classfiles and an assembler to create classfiles.<ref>[{{Cite web|url=https://github.com/Storyyeller/Krakatau |title=Storyyeller/Krakatau|date=1 June 2024|accessdate=2 homeJune page]2024|via=GitHub}}</ref>

*Lilac, an assembler and disassembler for the [[Java virtual machine]].<ref>[http{{Cite web|url=https://lilac.sourceforge.net /|title=Lilac home- a Java assembler|website=lilac.sourceforge.net|accessdate=2 June page]2024}}</ref>

Others have developed compilers, for different programming languages, to target the Java virtual machine, such as:

*[[ColdFusion Markup Language|ColdFusion]]

*[[JRuby]] and [[Jython]], two [[scripting language]]s based on [[Ruby (programming language)|Ruby]] and [[Python (programming language)|Python]]

*[[Groovy (programming language)|Apache Groovy]], aoptionally [[scriptingtyped and dynamic general-purpose language]], with static-typing and basedstatic oncompilation Javacapabilities

*[[Scala (programming language)|Scala]], a type-safe general-purpose programming language supporting object-oriented and functional programming

*[[JGNAT]] and AppletMagic, compile from the language [[Ada (programming language)|Ada]] to Java bytecode

*[[Java virtual machine#C to bytecode compilers|C to Java byte-code compiler]]s {{dead link|date=December 2018}}

*[[Clojure]], a functional, immutable, general-purpose programming language in the [[Lisp (programming language)|Lisp]] family with a strong emphasis on concurrency

*[[Kawa (Scheme implementation)|Kawa]], an implementation of the [[Scheme (programming language)|Scheme]] programming language, also a dialect of [[Lisp (programming language)|Lisp]].

*[[MIDletPascal]]

*[[JavaFX Script]] code is compiled to Java bytecode

*[[Kotlin (programming language)|Kotlin]], a statically-typed general-purpose programming language with type inference

*[[Object Pascal]] source code is compiled to Java bytecode using the [[Free Pascal]] 3.0+ compiler.<ref>[http{{Cite web|url=https://wiki.freepascal.org/FPC_New_Features_3.0#Support_for_the_Java_Virtual_Machine_and_Dalvik_targets|title=FPC FreeNew PascalFeatures 3.0.0 - Free Pascal wiki|website=wiki.freepascal.org|accessdate=2 releaseJune notes]2024}}</ref><ref>[http{{Cite web|url=https://wiki.freepascal.org/FPC_JVM|title=FPC JVM - Free Pascal JVMwiki|website=wiki.freepascal.org|accessdate=2 June Target]2024}}</ref>

== Execution ==

There are several machines available today, both free and commercial products.

{{Further|Java virtual machine}}

IfThere executingare several Java virtual machines available today to execute Java bytecode, both free and commercial products. If executing bytecode in a Java virtual machine is undesirable, a developer can also compile Java source code or bytecode directly to native machine code with tools such as the [[GNU Compiler for Java]] (GCJ). Some processors can execute Java bytecode natively. Such processors are termed ''[[Java processor]]s''.

== Support for dynamic languages ==

{{Further information|List of JVM languages}}

The [[Java virtual machine]] provides some support for [[Type system#Dynamic typing|dynamically typed languages]]. Most of the extant JVM instruction set is [[Type system#Static typing|statically typed]] - in the sense that method calls have their signatures type-checked at [[compile time]], without a mechanism to defer this decision to [[Run time (program lifecycle phase)|run time]], or to choose the method dispatch by an alternative approach.<ref>{{cite web

| url=httphttps://headius.blogspot.com/2007/01/invokedynamic-actually-useful.html

| title=InvokeDynamic: Actually Useful?

| date=2007-01-03

|last=Nutter|first=Charles

| accessdateaccess-date=2008-01-25}}</ref>

[[Java Community Process|JSR]] 292 (''Supporting Dynamically Typed Languages on the Java&trade; Platform'')<ref>[http{{Cite web|url=https://www.jcp.org/en/jsr/detail?id=292|title=The seeJava Community Process(SM) Program - JSRs: Java Specification Requests - detail JSR# 292]|website=www.jcp.org|accessdate=2 June 2024}}</ref> added a new <code>invokedynamic</code> instruction at the JVM level, to allow method invocation relying on dynamic [[Type system#Type checking|type checking]] (instead of the extant statically type-checked <code>invokevirtual</code> instruction). The [[Da Vinci Machine]] is a prototype virtual machine implementation that hosts JVM extensions aimed at supporting dynamic languages. All JVMs supporting [[Java Platform, Standard Edition|JSE]] 7 also include the <code>invokedynamic</code> opcode.

== See also ==

{{Portal|JavaComputer programming}}

<!---♦♦♦ Please keep the list in alphabetical order ♦♦♦--->

* [[Java bytecode instruction listings]]

* [[Byte Code Engineering Library]]

* [[Common Intermediate Language]] (CIL), Microsoft's rival to Java bytecode

* [[Java backporting tools]]

* [[Java class file]]

* [[ListJava ofvirtual JVM languagesmachine]]

* [[Java backporting tools]]

* [[C to Java Virtual Machine compilers]]

* [[JStik]]

* [[Common Intermediate Language]] (CIL), Microsoft's rival to Java bytecode

* [[ObjectWeb ASM]]

* [[List of Java bytecode instruction listingsinstructions]]

* [[List of JVM languages]]

== References ==

Line 162 ⟶ 171:

== External links ==

{{Wikibooks|Java Programming|Byte Code|Java bytecode}}

* [http://docs.oracle.com/javase/specs/jvms/se7se8/html/ Oracle's Java Virtual Machine Specification]

* [http://www.is-research.de/info/vmlanguages/ Programming Languages for the Java Virtual Machine]

* [https://web.archive.org/web/20130618025348/http://www.drgarbage.com/bytecode-visualizer.html Bytecode Visualizer – bytecode viewer and debugger (free Eclipse plugin)]

* [https://web.archive.org/web/20090809232522/http://www.adaptj.com/main/stacktrace AdaptJ StackTrace – bytecode level debugging with a full control of the stack, the local variables, and the execution flow]

* [http://lulachronicles.blogspot.com Java Class Unpacker – plugin for Total Commander, it lets open class files as compressed archives and see fields and methods as files. The bytecode can be viewed as text using F3]

{{Java (Sun)}}

[[Category:Java platform|Bytecodes]]

[[Category:Assembly languages]]

[[Category:Java platform|Bytecodes]]

[[Category:Bytecodes]]