本文提到的所有问题(字节顺序、传递到编译器的选项等等)都有可能与移植有关。
All issues mentioned in this article might be relevant (byte-ordering, the options passed to the compiler, and so forth).
编译器为每个A类型的对象分配1个字节。
编译器在源代码中查找各种模式以便将源代码表达式转换为字节码。
A compiler looks for various patterns in the source to convert the source code expressions into bytecodes.
接下来，生成的源代码再经过其他标准的编译器编译并使用IKVM库引用来生成MSIL字节码。
The resulting source code then passes through the rest of the standard compiler phases producing MSIL byte-code with IKVM library references.
我们在构建一个新的编译器和中间表述，这样在我们生成JVM字节码前更容易做一些优化。
We've continued building a new compiler and intermediate representation that will be easier to optimize before we generate JVM bytecode.
这很方便，如果不支持的话，编译器会一次生成基本兼容的字节码。
It is convenient, if unsupported, and the compiler generates mostly compatible bytecode in a single pass.
的确如此，但这仅意味着根据正式名引用类的工作由编译器和字节码完成。
This is true, but it merely means that the work of referencing the class by its formal name falls to the compiler and bytecode.
这些变化包括：对编译器代码生成进行完全重写，添加用源代码增强代替字节码增强的选项。
These changes include a complete rewrite of the binding compiler code generation, with an added option for using source code enhancement as an alternative to bytecode enhancement.
使用字节码和编译器后端
字节码增强器使用classworking技术来修改由JD k 5.0编译器生成的类文件，使得这些类可以用于旧版J VM。
The bytecode enhancer USES classworking techniques to modify the class files generated by the JDK 5.0 compiler, making these classes usable with older JVMs.
这个配置由JiBX框架的绑定编译器组件处理，它实现了编译后的类的实际字节码增强。
This configuration is processed by a binding compiler component of the JiBX framework, which implements the actual bytecode enhancement of the compiled classes.
Perl编译器通过使用所生成的字节码，以一种不同的方式输出结果。
The Perl compiler works by taking the generated bytecode and then outputting the results in a variety of different ways.
缺点：使用一个“虚拟机”来运行可移植的字节码而非本地机器码，程序将比真正编译器慢。
Disadvantages: Uses a "virtual machine" to run portable byte-code rather than native machine code, so apps are slower than true compilers.
编译器输出字节码，经常输出到一个JAR文件里。
编译器输出字节码，经常输出到一个JAR文件里。
应用推荐