Searched refs:compiler (Results 1 – 25 of 40) sorted by relevance
12
2 org.eclipse.jdt.core.compiler.annotation.nonnull=com.android.annotations.NonNull3 org.eclipse.jdt.core.compiler.annotation.nonnullbydefault=com.android.annotations.NonNullByDefault4 org.eclipse.jdt.core.compiler.annotation.nonnullisdefault=disabled5 org.eclipse.jdt.core.compiler.annotation.nullable=com.android.annotations.Nullable6 org.eclipse.jdt.core.compiler.annotation.nullanalysis=enabled7 org.eclipse.jdt.core.compiler.codegen.inlineJsrBytecode=enabled8 org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.69 org.eclipse.jdt.core.compiler.codegen.unusedLocal=preserve10 org.eclipse.jdt.core.compiler.compliance=1.611 org.eclipse.jdt.core.compiler.debug.lineNumber=generate[all …]
21 LOCAL_MODULE := databinding-compiler22 LOCAL_SRC_FILES := prebuilds/$(my_prebuilt_version)/databinding-compiler-all.jar
3 include ':compiler'
152 Compiler *compiler = pCompilerDriver.getCompiler(); in ConfigCompiler() local205 Compiler::ErrorCode result = compiler->config(*config); in ConfigCompiler()266 Compiler compiler; in main() local
22 cross-compiler in order to add support to Android for it.</p>25 cross-compiler in the {@code CC} environment variable.</p>93 <p>There are two ways to invoke the compiler. One method is simple, and leaves most of the lifting97 <p>The simplest way to build is by invoking the appropriate compiler directly from the command198 <td>mips64 compiler</td>202 <td>mips GCC 4.8 compiler</td>206 <td>x86 GCC 4.8 compiler</td>210 <td>x86_64 GCC 4.8 compiler</td>214 <td>mips GCC 4.8 compiler</td>423 <li>{@code -v} to dump commands associated with compiler driver issues</li>[all …]
63 <p>This variable stores a set of C compiler flags that the build system passes to the compiler98 <p>This variable contains a set of C++ compiler flags that the build system passes to the compiler195 compiler. Version 4.9 is the default for 64-bit ABIs, and 4.8 is the default for 32-bit ABIs.
353 module. Only list the files that the build system actually passes to the compiler, since the build381 It enables the right compiler and linker flags during the build process. For prebuilt binaries,387 {@code LOCAL_CPPFLAGS} causes the compiler to use all specified flags for all modules, regardless435 <p>This optional variable sets compiler flags for the build system to pass when building C459 <p>An optional set of compiler flags that will be passed when building C++461 compiler's command-line.</p>623 compiler error if a non-constant format string is used in a {@code printf}-style function.</p>630 <p>This variable records a set of C/C++ compiler flags to add to the {@code LOCAL_CFLAGS} definition653 <p>Here, the build system passes the flags {@code -DFOO=1} and {@code -DBAR=2} to the compiler when663 to the compiler when building {@code foo/foo.c}. To build locally, use {@code LOCAL_CFLAGS}[all …]
155 functions from the compiler's {@code libgcc.a} static library.</p>196 enforce the rule that the compiler must pass all double values in core register pairs during221 <p>The compiler compiles all code with hard-float, and links it with {@code libm_hard.a}.238 <li>Instructions normally generated by GCC with compiler flags such as the following:252 <p> For more information on compiler flags, particularly related to performance optimization,296 compiler flags:</p>314 <p> For more information on compiler flags, particularly related to performance optimization,
24 As a result, a specific compiler flag enables the use of GCC ARM NEON intrinsics and VFPv3-D32
92 <p>In such a case, you need to provide the header and its include path to the compiler when you
57 the corresponding "low performance" compiler warning.</li>
14 - llvm-rs-cc (slang frontend compiler)
48 pom.artifactId = 'compiler'
205 <li>Fixed an internal compiler error with GCC4.9/aarch64 that was causing the following208 internal compiler error: in simplify_const_unary_operation, at simplify-rtx.c:1539212 <li>Fixed an internal compiler error with GCC4.9/mips involving inline-assembly. (Issue294 <code>include-fixed/linux/compiler.h</code> headers from the GCC compiler.407 <li>GCC 4.9 is the default compiler for 64-bit ABIs. Clang is currently version 3.4.440 <li>Added GCC 4.9 compilers to the 32-/64-bit ABIs. GCC 4.9 is the default (only) compiler466 requires the use of a different compiler. Note that Clang 3.3 is untested.</li>582 <li>Added support for the Clang 3.4 compiler. The584 still the default compiler.</li>780 <pre>cc1: internal compiler error: in common_handle_option, at[all …]
74 cd $MY_ANDROID_DIR/external/compiler-rt && mma -j$NUM_CORES && cd - || exit 3
47 <acronym title="Just In Time compiler">JIT</acronym>: the best128 <p>The compiler generates a class initializer method, called162 object oriented languages like C# and Java, because the compiler can172 <p>Without a <acronym title="Just In Time compiler">JIT</acronym>,284 members. To bridge the gap, the compiler generates a couple of synthetic
895 barrier instruction. Second, it tells the compiler that it is not allowed to898 section. Without this <em>compiler reorder barrier</em>, the compiler has a916 <p>We perform our second CPU/compiler memory barrier immediately960 <code>atomic_release_store</code> on x86 is therefore just a compiler reorder963 <p>The second optimization mostly applies to the compiler (although some CPUs,989 <p>A full compiler reorder barrier in the atomic ops will ensure that the991 allowing the compiler to interleave instructions can improve performance. Loads1043 how the compiler is allowed to reorder code.</p>1063 very useful. The compiler will not omit or reorder accesses to volatile1070 (explicit compiler reorder barriers may be required). There are no atomicity[all …]
71 compiled by the Java compiler and .class files are output.</li>
228 <li>For managing the platform's JIT compiler:231 …gt;</code> element. Boolean value that specifies whether to disable JIT compiler optimizations whe…
25 * a *just-in-time bitcode compiler*, which translates the LLVM bitcode
META-INF/ META-INF/MANIFEST.MF android/ android/databinding/ android/ ...
22 Java compiler still creates an executable stub for the virtual machine to run.
95 <p>Adding this attribute will cause an error in the compiler, because the attribute is unknown to
63 <code>llvm</code> compiler that runs as part of an Android build. When your application65 <code>llvm</code> compiler that resides on the device. The machine code is optimized for the570 in the first place. A compiler error is generated if you try to declare a non-static, global