search for: data_x

Dear List members, its me again, fighting with lattice graphics. I am trying to plot a world map, add some points on different locations with different colors and add a legend, but did not succeed yet with the legend. Here is my code: library(fields) # Data for demonstration data_x = c(0,50,60) data_y = c(0,0,0) cols???= c(1,2,3) data(world.dat) #print map all=xyplot(world.dat$y? ~ world.dat$x, type=c('l'),col="black",xlab="",ylab="", ???ylim=c(-55,80),xlim=c(-170,175),pch=20,cex=0.2, ???auto.key = list(x=0,y=0,text=c('test1',...

...otor <- sort(unique(cleaner_1[,5])) # find all motors for platform 1 sorted for(i in 1: length(Motor)){ row_vector <- which(cleaner_1[,5]==Motor[i]) # find the first motor cleaner_type_1 <- cleaner_1[row_vector,] # store it in cleaner_type_1 Data_x <-cleaner_type_1[9] Data_y <-cleaner_type_1[10] hist(Data_x[,], probability=TRUE, breaks=5, main=data_header[9]) savePlot(filename = paste(c("C:/pow",j,"_",i), collapse="") ,type = "eps") # Save plot with order no i

Oh, I appologize that I should not have asked about __main() ---- it appears in FAQ. But the question remains that why call to __main() can alias stack location? I think the memory location pointed by data_X pointers are not visible to __main(). In comparison, calls to printf() do not have similar effect. On 5/14/06, Nai Xia <nelson.xia at gmail.com> wrote: > > In a code segment of my pass plugin, I try to gather AliasSets for all > StoreInst, LoadInst and CallInst instructions in a...

...ith MOD/REF logic for functions as below: i. inComplete nodes may MODREF by all function. ii. external function does not MOD/REF any complete node. iii if any function MOD/REF a node then all function considered as MOD/REF the node. In other words, if I only use -steens-aa and the data_XXXs are all external global variables( and so inComplete ), the call to printf will make the same effect, which I have tested it. Am I right ? :) On Monday 15 May 2006 12:52, Chris Lattner wrote: > On Mon, 15 May 2006, Nai Xia wrote: > > Thank you very much for your detailed help. >...

In a code segment of my pass plugin, I try to gather AliasSets for all StoreInst, LoadInst and CallInst instructions in a function. Some behaviors of the pass puzzled me. Below is the *.ll of the test program which I run the pass on, it was get with "llvm-gcc -Wl,--disable-opt" from a rather simple *.c program. ---------------------------------- ; ModuleID = 'ptralias.bc'

On Tuesday 16 May 2006 03:19, Chris Lattner wrote: > On Mon, 15 May 2006, Nai Xia wrote: > > > In other words, if I only use -steens-aa and the data_XXXs are all > > external global variables( and so inComplete ), > > Sounds right! > > > the call to printf will > > make the same effect, which I have tested it. > > > > Am I right ? :) > > If you've tested it then, yes you're right :). I ha...

...gt;>> Oh, I appologize that I should not have asked about __main() ---- it appears >>>>>>> in FAQ. >>>>>>> But the question remains that why call to __main() can alias stack location? >>>>>>> I think the memory location pointed by data_X pointers are not visible to >>>>>>> __main(). >>>>>>> In comparison, calls to printf() do not have similar effect. >>>>>> >>>>>> First, some background: -steens-aa and -anders-aa work reasonable well, >>>>>...

On Mon, 15 May 2006, Nai Xia wrote: > In other words, if I only use -steens-aa and the data_XXXs are all > external global variables( and so inComplete ), Sounds right! > the call to printf will > make the same effect, which I have tested it. > > Am I right ? :) If you've tested it then, yes you're right :). I haven't played with this stuff for a long time,...