Home
last modified time | relevance | path

Searched refs:aliasing (Results 1 – 25 of 279) sorted by relevance

12345678910>>...12

/external/eigen/doc/
DTopicAliasing.dox5 In %Eigen, aliasing refers to assignment statement in which the same matrix (or array or vector) ap…
7 mat.transpose();</tt> exhibit aliasing. The aliasing in the first example is harmless, but the alia…
8 second example leads to unexpected results. This page explains what aliasing is, when it is harmful…
16 Here is a simple example exhibiting aliasing:
31 This assignment exhibits aliasing: the coefficient \c mat(1,1) appears both in the block
47 vec.head(n)</tt> and <tt>mat = mat.block(i,j,r,c)</tt> exhibit aliasing.
49 In general, aliasing cannot be detected at compile time: if \c mat in the first example were a bit …
50 then the blocks would not overlap, and there would be no aliasing problem. However, %Eigen does det…
51 instances of aliasing, albeit at run time. The following example exhibiting aliasing was mentioned…
63 Again, the output shows the aliasing issue. However, by default %Eigen uses a run-time assertion to…
[all …]
/external/clang/test/Frontend/
Dopencl.cl9 // RUN: %clang_cc1 -cl-std=CL1.1 -cl-strict-aliasing -fblocks %s 2>&1 | FileCheck --check-prefix=CH…
10 // RUN: %clang_cc1 -cl-std=CL1.2 -cl-strict-aliasing -fblocks %s 2>&1 | FileCheck --check-prefix=CH…
11 // RUN: %clang_cc1 -cl-std=CL2.0 -cl-strict-aliasing %s 2>&1 | FileCheck --check-prefix=CHECK-INVAL…
25 …LID-OPENCL-VERSION11: warning: OpenCL version 1.1 does not support the option '-cl-strict-aliasing'
26 …LID-OPENCL-VERSION12: warning: OpenCL version 1.2 does not support the option '-cl-strict-aliasing'
27 …LID-OPENCL-VERSION20: warning: OpenCL version 2.0 does not support the option '-cl-strict-aliasing'
/external/icu/icu4c/source/test/testdata/
Dtestaliases.txt11 // This is a test resource to check whether the aliasing mechanism works
20 // aliasing nonexist position
23 // aliasing to another resource
32 // aliasing using position
35 // aliasing arrays
42 // Test aliasing parts of an array using position
/external/libffi/m4/
Dax_cc_maxopt.m420 # Note also that the flags assume that ANSI C aliasing rules are followed
21 # by the code (e.g. for gcc's -fstrict-aliasing), and that floating-point
147 # -fstrict-aliasing for gcc-2.95+
148 AX_CHECK_COMPILE_FLAG(-fstrict-aliasing,
149 CFLAGS="$CFLAGS -fstrict-aliasing")
/external/python/cpython2/Modules/_ctypes/libffi/m4/
Dax_cc_maxopt.m420 # Note also that the flags assume that ANSI C aliasing rules are followed
21 # by the code (e.g. for gcc's -fstrict-aliasing), and that floating-point
147 # -fstrict-aliasing for gcc-2.95+
148 AX_CHECK_COMPILE_FLAG(-fstrict-aliasing,
149 CFLAGS="$CFLAGS -fstrict-aliasing")
/external/llvm/test/Analysis/TypeBasedAliasAnalysis/
Dprecedence.ll10 ; Test for simple MustAlias aliasing.
25 ; Test for PartialAlias aliasing. GVN doesn't yet eliminate the load
/external/adhd/defs/
Dc.mk81 -Wstrict-aliasing \
82 -Wstrict-aliasing=3 \
/external/swiftshader/third_party/llvm-7.0/llvm/test/Analysis/TypeBasedAliasAnalysis/
Dprecedence.ll10 ; Test for simple MustAlias aliasing.
25 ; Test for PartialAlias aliasing. GVN doesn't yet eliminate the load
/external/swiftshader/third_party/LLVM/test/Analysis/TypeBasedAliasAnalysis/
Dprecedence.ll10 ; Test for simple MustAlias aliasing.
25 ; Test for PartialAlias aliasing. GVN doesn't yet eliminate the load
/external/swiftshader/third_party/llvm-7.0/llvm/test/CodeGen/Hexagon/
Dtrivialmemaliascheck.ll4 ; non-aliasing. However, there are some cases where the scheduler cannot
10 ; dependence due to aliasing between the two instructions.
/external/swiftshader/third_party/llvm-7.0/llvm/test/CodeGen/ARM/
Dsmlad7.ll4 ; aliasing one of the mul load operands. Arguments are now annotated with
29 ; Store inserted here, aliasing only with loads from 'arrayidx'.
Dsmlad6.ll4 ; instruction possibly aliasing any mul load operands; arguments are passed
29 ; Store inserted here, aliasing with arrayidx, arrayidx1, arrayidx3
/external/ltp/include/mk/
Dconfig.mk.default64 # Please see README.mk-devel about -fstrict-aliasing.
65 OPT_CFLAGS ?= -O2 -fno-strict-aliasing -pipe
Dconfig.mk.in67 # Please see README.mk-devel about -fstrict-aliasing.
68 OPT_CFLAGS ?= -O2 -fno-strict-aliasing -pipe
/external/linux-kselftest/tools/testing/selftests/ia64/
D.gitignore1 aliasing-test
DMakefile2 TEST_PROGS := aliasing-test
/external/clang/test/CodeGenOpenCL/
Dcl-strict-aliasing.cl1 // RUN: %clang_cc1 -x cl -emit-llvm -cl-strict-aliasing < %s
/external/swiftshader/third_party/llvm-7.0/llvm/test/Transforms/LoadStoreVectorizer/AMDGPU/
Dstore_with_aliasing_load.ll3 ; Check that, in the presence of an aliasing load, the stores preceding the
4 ; aliasing load are safe to vectorize.
/external/iputils/Modules/
DMakefile5 CCOPT=-O2 -Wstrict-prototypes -Wall -Werror -fno-strict-aliasing -fno-common
/external/libcxxabi/cmake/
Dconfig-ix.cmake55 check_cxx_compiler_flag(-fstrict-aliasing LIBCXXABI_HAS_FSTRICT_ALIASING_FLAG)
62 check_cxx_compiler_flag(-Wstrict-aliasing LIBCXXABI_HAS_WSTRICT_ALIASING_FLAG)
/external/clang/test/Driver/
Dopencl.cl6 // RUN: %clang -S -### -cl-strict-aliasing %s 2>&1 | FileCheck --check-prefix=CHECK-STRICT-ALIASING…
23 // CHECK-STRICT-ALIASING: "-cc1" {{.*}} "-cl-strict-aliasing"
/external/libunwind_llvm/cmake/
Dconfig-ix.cmake62 check_cxx_compiler_flag(-fstrict-aliasing LIBUNWIND_HAS_FSTRICT_ALIASING_FLAG)
69 check_cxx_compiler_flag(-Wstrict-aliasing LIBUNWIND_HAS_WSTRICT_ALIASING_FLAG)
/external/u-boot/arch/nds32/
Dconfig.mk18 PLATFORM_RELFLAGS += -fno-strict-aliasing -fno-common -mrelax
/external/v8/tools/gcmole/
DMakefile37 -fno-rtti -fPIC -Woverloaded-virtual -Wcast-qual -fno-strict-aliasing \
/external/u-boot/arch/riscv/
Dconfig.mk34 PLATFORM_RELFLAGS += -fno-strict-aliasing -fno-common -gdwarf-2 -ffunction-sections

12345678910>>...12