Displaying 3 results from an estimated 3 matches for "74580".
Did you mean:
74,80
2018 Apr 11
2
Possible \uxxx typos in documents
I found a few occurrences of "\uxxx" which should probably have
one more "x". A patch follows:
Index: doc/manual/R-ints.texi
===================================================================
--- doc/manual/R-ints.texi (revision 74580)
+++ doc/manual/R-ints.texi (working copy)
@@ -1277,11 +1277,11 @@
we have to a universal format. For those that do not (for example those
lacking a powerful enough @code{iconv}), it is likely that they work in
Latin-1, the old @R{} assumption. Then the parser can return a
-UTF-8-encoded string...
2009 Jun 30
0
[LLVMdev] Limitations of Alias Analysis?
On Mon, Jun 29, 2009 at 7:40 PM, Wenzhi Tao<linus_wind at zju.edu.cn> wrote:
> The result of -aa-eval:
>
> MayAlias: %struct.Location* %0, %struct.Location* %1
> MayAlias: %struct.Location* %0, %struct.Location* %2
> MayAlias: %struct.Location* %1, %struct.Location* %2
I'm getting NoAlias with the given steps; are you using trunk LLVM?
-Eli
2009 Jun 30
2
[LLVMdev] Limitations of Alias Analysis?
Hi,
Thanks for your advice. I have tried this way:
opt -mem2reg test.bc -o mem2reg.bc
llvm-dis mem2reg.bc
opt -functionattrs -basicaa -aa-eval -print-all-alias-modref-info
mem2reg.bc
The content of main() in mem2reg.ll:
define i32 @main() nounwind {
entry:
%"alloca point" = bitcast i32 0 to i32 ; <i32> [#uses=0]
%0 = call %struct.Location* @getNewLocation(i32 0, i32