Examine individual changes

'{{Short description|Instruction set of the Java virtual machine}} {{short lead|date=August 2022}} In computing, '''Java bytecode''' is the [[bytecode]]-structured [[instruction set]] of the [[Java virtual machine]] (JVM), a [[virtual machine]] that enables a computer to run programs written in the [[Java (programming language)|Java]] programming language and several other programming languages, see [[List of JVM languages]]. == Relation to Java == A [[Java (programming language)|Java]] programmer does not need to be aware of or understand Java bytecode at all. 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>{{Cite web |title=IBM Developer |url=https://developer.ibm.com/languages/java/ |url-status=live |access-date=20 February 2006 |website=developer.ibm.com}}</ref> == Instruction set architecture == 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}} The operand stack is used for 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 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 |- | <code>l</code> || long |- | <code>s</code> || short |- | <code>b</code> || byte |- | <code>c</code> || character |- | <code>f</code> || float |- | <code>d</code> || double |- | <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 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 index in the local variable 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 local variables beyond 3 the suffix is dropped and operands must be used. == Example == Consider the following Java code: <syntaxhighlight lang="java"> outer: for (int i = 2; i < 1000; i++) { for (int j = 2; j < i; j++) { if (i % j == 0) continue outer; } System.out.println (i); } </syntaxhighlight> A Java compiler might translate the Java code above into bytecode as follows, assuming the above was put in a method: <syntaxhighlight lang="jasmin"> 0: iconst_2 1: istore_1 2: iload_1 3: sipush 1000 6: if_icmpge 44 9: iconst_2 10: istore_2 11: iload_2 12: iload_1 13: if_icmpge 31 16: iload_1 17: iload_2 18: irem 19: ifne 25 22: goto 38 25: iinc 2, 1 28: goto 11 31: getstatic #84; // Field java/lang/System.out:Ljava/io/PrintStream; 34: iload_1 35: invokevirtual #85; // Method java/io/PrintStream.println:(I)V 38: iinc 1, 1 41: goto 2 44: return</syntaxhighlight> == Generation == {{Further|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 was 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://jasmin.sourceforge.net Jasmin home page<!-- Bot generated title -->]</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>[https://www.javaworld.com/article/2072355/core-java/learn-to-speak-jamaican.html Jamaica: The Java virtual machine (JVM) macro assembler<!-- Bot generated title -->]</ref> *Krakatau Bytecode Tools, currently contains three tools: a decompiler and disassembler for Java classfiles and an assembler to create classfiles.<ref>[https://github.com/Storyyeller/Krakatau Krakatau home page]</ref> *Lilac, an assembler and disassembler for the [[Java virtual machine]].<ref>[http://lilac.sourceforge.net Lilac home page]</ref> Others have developed compilers, for different programming languages, to target the Java virtual machine, such as: *[[ColdFusion]] *[[JRuby]] and [[Jython]], two [[scripting language]]s based on [[Ruby (programming language)|Ruby]] and [[Python (programming language)|Python]] *[[Groovy (programming language)|Apache Groovy]], optionally typed and dynamic general-purpose language, with static-typing and static compilation capabilities *[[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://wiki.freepascal.org/FPC_New_Features_3.0#Support_for_the_Java_Virtual_Machine_and_Dalvik_targets Free Pascal 3.0 release notes]</ref><ref>[http://wiki.freepascal.org/FPC_JVM Free Pascal JVM Target]</ref> == Execution == {{Further|Java virtual machine}} There are several Java virtual machines available today to execute Java bytecode, both free and commercial products. If executing bytecode in a 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|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=http://headius.blogspot.com/2007/01/invokedynamic-actually-useful.html | title=InvokeDynamic: Actually Useful? | date=2007-01-03 |last=Nutter|first=Charles | access-date=2008-01-25}}</ref> [[Java Community Process|JSR]] 292 (''Supporting Dynamically Typed Languages on the Java Platform'')<ref>[http://www.jcp.org/en/jsr/detail?id=292 see JSR 292]</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|Computer programming}} * [[List of Java bytecode instructions]] * [[Java class file]] * [[List of JVM languages]] * [[Java backporting tools]] * [[Java virtual machine]] * [[JStik]] * [[Common Intermediate Language]] (CIL), Microsoft's rival to Java bytecode * [[ObjectWeb ASM]] * [[Byte Code Engineering Library]] * [https://coderharish.blogspot.com/2023/03/from-source-code-to-bytecode.html From Source Code to Bytecode: Understanding the Compilation Process in Java] == References == {{Reflist|2}} == External links == {{Wikibooks|Java Programming|Byte Code|Java bytecode}} * [http://docs.oracle.com/javase/specs/jvms/se8/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:Assembly languages]] [[Category:Java platform|Bytecodes]] [[Category:Bytecodes]]'