Displaying 3 results from an estimated 3 matches for "xanalyzer".
Did you mean:
analyzer
2010 Oct 28
0
[LLVMdev] strict aliasing and LLVM
2010/10/27 Xinliang David Li <xinliangli at gmail.com>:
> Thanks. Just built clang and saw the meta data and annotations on the memory
> accesses -- is any opt pass consuming the information?
The tests in test/Analysis/TypeBasedAliasAnalysis suggest that at
least licm is using it. Also note that
lib/Analysis/TypeBasedAliasAnalysis.cpp defines as enable-tbaa option
that is off by
2010 Oct 28
2
[LLVMdev] strict aliasing and LLVM
Thanks. Just built clang and saw the meta data and annotations on the memory
accesses -- is any opt pass consuming the information?
By the way the build instruction in this page
http://clang.llvm.org/get_started.html needs to be updated -- it recommends
config (with default settings) and build llvm in the source dir -- it leaves
some 'sticky' generated files in the source dir leading to
2010 Oct 28
4
[LLVMdev] strict aliasing and LLVM
...it. Also note that
> lib/Analysis/TypeBasedAliasAnalysis.cpp defines as enable-tbaa option
> that is off by default.
>
>
I tried the option -- no much differences in the generated code.
A related question: how to pass the llvm specific options from clang driver?
It supports -Wl, -Wa, -Xanalyzer etc, but there is no documentation on how
to pass -enable-tbaa to opt driver.
llvmc supports -Wo, option, but the option specified after -Wo, seems to be
dropped. Another thing, when using -clang option to llvmc, I got link
errors even when -c or -S is specified:
clang -x c foo.c -emit-llvm-bc...