Package com.strobel.reflection.emit
Enum Class CompilationTarget
- All Implemented Interfaces:
Serializable
,Comparable<CompilationTarget>
,Constable
-
Nested Class Summary
Nested classes/interfaces inherited from class java.lang.Enum
Enum.EnumDesc<E extends Enum<E>>
-
Enum Constant Summary
Enum ConstantsEnum ConstantDescriptionJ2SE1.4 = Merlin.The following are undocumented transitional targets that we had used to test VM fixes in update releases.Tiger.JDK 6.JDK 7.Support for the JSR14 prototype compiler (targeting 1.4 VMs augmented with a few support classes). -
Field Summary
FieldsModifier and TypeFieldDescriptionstatic final CompilationTarget
final int
private static final CompilationTarget
private static CompilationTarget
final int
final String
private static final Map
<String, CompilationTarget> -
Constructor Summary
ConstructorsModifierConstructorDescriptionprivate
CompilationTarget
(String name, int majorVersion, int minorVersion) -
Method Summary
Modifier and TypeMethodDescriptionboolean
Starting in 1.5, the compiler uses an array type as the qualifier for method calls (such as clone) where required by the language and VM spec.boolean
For bootstrapping, we use J2SE1.4's wrapper class constructors to implement boxing.boolean
Although we may not have support for class literals, should we avoid initializing the class that the literal refers to? See 4468823boolean
Return true if cldc-style stack maps need to be generated.boolean
Do we generate "empty" stackmap slots after double and long?boolean
Beginning in -target 6, we generate stackmap attribute in compact format.boolean
Does the VM have direct support for class literals?boolean
In J2SE1.5.0, we introduced the "EnclosingMethod" attribute for improved reflection support.boolean
Although we may not have support for class literals, when we throw a NoClassDefFoundError, should we initialize its cause?boolean
Does the VM support an invokedynamic instruction?boolean
For bootstrapping, we use J2SE1.4's java.util.Collection instead of java.lang.Iterable.boolean
Does the VM support polymorphic method handle invocation? Affects the linkage information output to the classfile.boolean
Beginning in 1.4, we take advantage of the possibility of emitting code to initialize fields before calling the superclass constructor.boolean
Beginning after 1.2, we follow the binary compatibility rules for interface fields.boolean
Beginning in -target 1.5, we follow the binary compatibility rules for interface methods that redefine Object methods.boolean
Beginning in -target 6, package-info classes are marked synthetic.static CompilationTarget
static CompilationTarget
MAX()
static CompilationTarget
MIN()
boolean
Beginning with -target 1.2 we obey the JLS rules for binary compatibility, emitting as the qualifying type of a reference to a method or field the type of the qualifier.boolean
In -target 1.1 and earlier, the compiler is required to emit synthetic method definitions in abstract classes for interface methods that are not overridden.char
Return the character to be used in constructing synthetic identifiers, where not specified by the JLS.boolean
boolean
boolean
boolean
Sometimes we need to create a field to cache a value like a class literal of the assertions flag.boolean
Beginning in -target 1.4.2, we make synthetic variables package-private instead of private.boolean
Beginning in 1.5, we have an unsynchronized version of StringBuffer called StringBuilder that can be used by the compiler for string concatenation.boolean
Beginning in 1.5, we have flag bits we can use instead of marker attributes.boolean
static CompilationTarget
Returns the enum constant of this class with the specified name.static CompilationTarget[]
values()
Returns an array containing the constants of this enum class, in the order they are declared.
-
Enum Constant Details
-
JDK1_1
-
JDK1_2
-
JDK1_3
-
JDK1_4
J2SE1.4 = Merlin. -
JSR14
Support for the JSR14 prototype compiler (targeting 1.4 VMs augmented with a few support classes). This is a transitional option that will not be supported in the product. -
JDK1_4_1
The following are undocumented transitional targets that we had used to test VM fixes in update releases. We do not promise to retain support for them. -
JDK1_4_2
-
JDK1_5
Tiger. -
JDK1_6
JDK 6. -
JDK1_7
JDK 7.
-
-
Field Details
-
MIN
-
MAX
-
tab
-
name
-
majorVersion
public final int majorVersion -
minorVersion
public final int minorVersion -
DEFAULT
-
-
Constructor Details
-
CompilationTarget
-
-
Method Details
-
values
Returns an array containing the constants of this enum class, in the order they are declared.- Returns:
- an array containing the constants of this enum class, in the order they are declared
-
valueOf
Returns the enum constant of this class with the specified name. The string must match exactly an identifier used to declare an enum constant in this class. (Extraneous whitespace characters are not permitted.)- Parameters:
name
- the name of the enum constant to be returned.- Returns:
- the enum constant with the specified name
- Throws:
IllegalArgumentException
- if this enum class has no constant with the specified nameNullPointerException
- if the argument is null
-
MIN
-
MAX
-
lookup
-
requiresIproxy
public boolean requiresIproxy()In -target 1.1 and earlier, the compiler is required to emit synthetic method definitions in abstract classes for interface methods that are not overridden. We call them "Miranda" methods. -
initializeFieldsBeforeSuper
public boolean initializeFieldsBeforeSuper()Beginning in 1.4, we take advantage of the possibility of emitting code to initialize fields before calling the superclass constructor. This is allowed by the VM spec, but the verifier refused to allow it until 1.4. This is necesary to translate some code involving inner classes. See, for example, 4030374. -
obeyBinaryCompatibility
public boolean obeyBinaryCompatibility()Beginning with -target 1.2 we obey the JLS rules for binary compatibility, emitting as the qualifying type of a reference to a method or field the type of the qualifier. In earlier targets we use as the qualifying type the class in which the member was found. The following methods named *binaryCompatibility() indicate places where we vary from this general rule. -
arrayBinaryCompatibility
public boolean arrayBinaryCompatibility()Starting in 1.5, the compiler uses an array type as the qualifier for method calls (such as clone) where required by the language and VM spec. Earlier versions of the compiler qualified them by Object. -
interfaceFieldsBinaryCompatibility
public boolean interfaceFieldsBinaryCompatibility()Beginning after 1.2, we follow the binary compatibility rules for interface fields. The 1.2 VMs had bugs handling interface fields when compiled using binary compatibility (see 4400598), so this is an accommodation to them. -
interfaceObjectOverridesBinaryCompatibility
public boolean interfaceObjectOverridesBinaryCompatibility()Beginning in -target 1.5, we follow the binary compatibility rules for interface methods that redefine Object methods. Earlier VMs had bugs handling such methods compiled using binary compatibility (see 4392595, 4398791, 4392595, 4400415). The VMs were fixed during or soon after 1.4. See 4392595. -
usePrivateSyntheticFields
public boolean usePrivateSyntheticFields()Beginning in -target 1.4.2, we make synthetic variables package-private instead of private. This is to prevent the necessity of access methods, which effectively relax the protection of the field but bloat the class files and affect execution. -
useInnerCacheClass
public boolean useInnerCacheClass()Sometimes we need to create a field to cache a value like a class literal of the assertions flag. In -target 1.4.2 and later we create a new synthetic class for this instead of using the outermost class. See 4401576. -
generateCLDCStackmap
public boolean generateCLDCStackmap()Return true if cldc-style stack maps need to be generated. -
generateStackMapTable
public boolean generateStackMapTable()Beginning in -target 6, we generate stackmap attribute in compact format. -
isPackageInfoSynthetic
public boolean isPackageInfoSynthetic()Beginning in -target 6, package-info classes are marked synthetic. -
generateEmptyAfterBig
public boolean generateEmptyAfterBig()Do we generate "empty" stackmap slots after double and long? -
useStringBuilder
public boolean useStringBuilder()Beginning in 1.5, we have an unsynchronized version of StringBuffer called StringBuilder that can be used by the compiler for string concatenation. -
useSyntheticFlag
public boolean useSyntheticFlag()Beginning in 1.5, we have flag bits we can use instead of marker attributes. -
useEnumFlag
public boolean useEnumFlag() -
useAnnotationFlag
public boolean useAnnotationFlag() -
useVarargsFlag
public boolean useVarargsFlag() -
useBridgeFlag
public boolean useBridgeFlag() -
syntheticNameChar
public char syntheticNameChar()Return the character to be used in constructing synthetic identifiers, where not specified by the JLS. -
hasClassLiterals
public boolean hasClassLiterals()Does the VM have direct support for class literals? -
hasInvokedynamic
public boolean hasInvokedynamic()Does the VM support an invokedynamic instruction? -
hasMethodHandles
public boolean hasMethodHandles()Does the VM support polymorphic method handle invocation? Affects the linkage information output to the classfile. An alias forhasInvokedynamic
, since all the JSR 292 features appear together. -
classLiteralsNoInit
public boolean classLiteralsNoInit()Although we may not have support for class literals, should we avoid initializing the class that the literal refers to? See 4468823 -
hasInitCause
public boolean hasInitCause()Although we may not have support for class literals, when we throw a NoClassDefFoundError, should we initialize its cause? -
boxWithConstructors
public boolean boxWithConstructors()For bootstrapping, we use J2SE1.4's wrapper class constructors to implement boxing. -
hasIterable
public boolean hasIterable()For bootstrapping, we use J2SE1.4's java.util.Collection instead of java.lang.Iterable. -
hasEnclosingMethodAttribute
public boolean hasEnclosingMethodAttribute()In J2SE1.5.0, we introduced the "EnclosingMethod" attribute for improved reflection support.
-