search for: main0

Hi The following gotcha took me a long time to catch: f <- function(x, main0="red", ...){ par(col.axis=main0) plot(x,...) } f(1:10,main="title here") f(1:10,main="title here",main0="blue") I can't quite succinctly summarize why the second case works but the first one doesn't. -- Robin Hankin Uncertainty Analyst...

...s not the same program on every platform). For instance there is no such thing as O0/O1/O2 on OS X. > > > $clang -emit-llvm -c main.c -o main.bc > $clang -emit-llvm -c a.c -o a.bc > $llvm-ar cr main.lib main.bc > $llvm-ar cr a.lib a.bc > $clang -O0 -flto main.lib a.lib -o main0 > $clang -O1 -flto main.lib a.lib -o main1 > $clang -O2 -flto main.lib a.lib -o main2 > > $nm main0 > … > 00000000004005a0 t foo1 > 0000000000400580 t foo2 > 00000000004005e0 t foo3 > 0000000000400530 t foo4 > 0000000000400500 t frame_dummy > … > $ nm main1 &gt...

Hi Umesh, Thank you for the suggestion. I can use the "Brute force method " to narrow down the LTO wrong instructions here and there, but I still don't know why these wrong instructions are generated, and how to let Clang LTO don't generate those wrong instructions. I suspect the wrong code is caused by some LTO wrong optimization pass, so I hope to disable all optimizations in

...ce there is no such thing as >> O0/O1/O2 on OS X. >> >> >> >> >> $clang -emit-llvm -c main.c -o main.bc >> $clang -emit-llvm -c a.c -o a.bc >> $llvm-ar cr main.lib main.bc >> $llvm-ar cr a.lib a.bc >> $clang -O0 -flto main.lib a.lib -o main0 >> $clang -O1 -flto main.lib a.lib -o main1 >> $clang -O2 -flto main.lib a.lib -o main2 >> >> $nm main0 >> … >> 00000000004005a0 t foo1 >> 0000000000400580 t foo2 >> 00000000004005e0 t foo3 >> 0000000000400530 t foo4 >> 0000000000400500 t...