search for: qux

I have the following list of strings: x <- c("foo, foo2, foo3", "bar", "qux, qux1") what I want to do is to obtain foo, bar qux Namely for each element in the vector obtain only string before the first comma. What's the way to do it? - G.V. [[alternative HTML version deleted]]

Dear all, Suppose I have this data frame: > data_main V1 V2 foo 13.1 bar 12.0 qux 10.4 cho 20.33 pox 8.21 And I want to split the data into two parts first part are the one contain in the source array: > src [1] "bar" "pox" and the other one the complement. In the end we hope to get this two dataframes: > data_child1 V1 V2 bar 13.1 pox...

Dear all, I found that printing with 'cat' is very slow. For example in my machine this snippet __BEGIN__ # I need to resolve to use this type of loop. # because using write(), I need to create a matrix which # consumes so much memory. Note that "foo, bar, qux" object # is already very large (>2Gb) for ( s in 1:length(x) ) { cat(as.character(foo[s]),"\t",bar[s],"\t", qux[s],"\n") } __END__ for "x" of size ~1.5million, takes more than 10 hours to print. On my Linux 1994.MHz AMD processor. Is there any...

Hi all, The patch below is to fix a problem with unaligned memcpys. This program: void Bork() { int Qux[33] = {0}; } will currently produce this LLVM code on PPC64: @C.0.937 = internal constant [33 x i8] zeroinitializer define void @Bork() { entry: %Qux = alloca [33 x i8] %Qux1 = bitcast [33 x i8]* %Qux to i8* call void @llvm.memcpy.i64( i8* %Qux1, i8* getelementptr ([33 x i8]* @C.0.1173...

...odules `bar` and `baz`, I cannot import both of them in one `import` statement, I need two (`import('foo/bar'); import('foo/baz')`). I would like feedback on what people think is the best way of solving this. Here are some suggestions I?ve gathered; in the following, `foo`, `bar`, `qux` are (sub)modules. `f1`, `b1`, `b2`, `q1` ? are functions within the modules whose name starts with the same letter: (1) Use of Bash-like wildcards to specify which modules to import: ``` foo = import('foo') # Exposes `foo$f1`, `foo$f2` ?, but no submodules bar = import('foo/bar'...

...llvm.module.flags with the same ID to have the Override behavior but different values. An example of module flags: !0 = metadata !{ i32 1, metadata !"foo", i32 1 } !1 = metadata !{ i32 4, metadata !"bar", i32 37 } !2 = metadata !{ i32 2, metadata !"qux", i32 42 } !3 = metadata !{ i32 3, metadata !"qux", metadata !{ metadata !"foo", i32 1 } } !llvm.module.flags = !{ !0, !1, !2, !3 } - Metadata !0 has the ID !"foo" and the value '1'. The behavior if two or more !"foo" flags...

...me ID to >                  have the Override behavior but different values. > > An example of module flags: > >  !0 = metadata !{ i32 1, metadata !"foo", i32 1 } >  !1 = metadata !{ i32 4, metadata !"bar", i32 37 } >  !2 = metadata !{ i32 2, metadata !"qux", i32 42 } >  !3 = metadata !{ i32 3, metadata !"qux", >    metadata !{ >      metadata !"foo", i32 1 >    } >  } >  !llvm.module.flags = !{ !0, !1, !2, !3 } > > - Metadata !0 has the ID !"foo" and the value '1'. The behavior if two...

...have the Override behavior but different values. >> >> An example of module flags: >> >> !0 = metadata !{ i32 1, metadata !"foo", i32 1 } >> !1 = metadata !{ i32 4, metadata !"bar", i32 37 } >> !2 = metadata !{ i32 2, metadata !"qux", i32 42 } >> !3 = metadata !{ i32 3, metadata !"qux", >> metadata !{ >> metadata !"foo", i32 1 >> } >> } >> !llvm.module.flags = !{ !0, !1, !2, !3 } >> >> - Metadata !0 has the ID !"foo" and the value...

...ter the end of its lifetime." 2. We are trying to preserve 1st load and remove other loads now, because our test pattern can not get rid of "-fno-strict-aliasing", and additional loads hurt performance. We did some change in SROA::runOnAlloca, we try to do something like this: void qux(PB* _c) { PB* c; <= insert this for original code bar(&_c); c = _c; <= insert this for original code c->f1_ = 0; c->f2_ = 0.f; } Any opinions please let us know. Thanks! CY On Fri, Mar 18, 2016 at 11:24 PM, David Blaikie <dblaikie at gmail.com> wro...

Hi all, This patch is to fix a problem on PPC64 where an unaligned memcpy is generated. The testcase is this: $ cat testcase.c void Qux() { char Bar[11] = {0}; } What happens is that we produce LLVM code like this: call void @llvm.memcpy.i64( i8* %event_list2, i8* getelementptr ([11 x i8]* @C.103.30698, i32 0, i32 0), i64 11, i32 8 ) Notice that it has an 8-byte alignment. However, the Bar variable has 1-byte alignment, becau...

Dear R community, I have a question concerning recoding of a variable. I have a data set in which there is a variable devoted to the ISCO code describing the occupation of this certain individual (http://www.ilo.org/public/english/bureau/stat/isco/isco88/major.htm). Every type of occupation begins with a number and every number added to this number describes th occupation more detailed. Now my

...ow<-.ts > Consider the following examples of time series with ugly values: > x = 1:22 > foo = ts(x, start = 1.5, end = 106.5, frequency = 0.2) # a ts of 525 cycles > bar = ts(x, start = 2.5, end = 107.5, frequency = 0.2) # a ts of 525 cycles > starting 5 cycles later than foo > qux = ts(x, start = 2.5, end = 102.5, frequency = 0.2) # a ts of 500 cycles > starting 5 cycles later than foo > > # extraction works fine > window(foo, start = 20, end = 30) # works fine > window(bar, start = 20, end = 30) # works fine > window(qux, start = 20, end = 30) # works...

...> have the Override behavior but different values. > > An example of module flags: > > !0 = metadata !{ i32 1, metadata !"foo", i32 1 } > !1 = metadata !{ i32 4, metadata !"bar", i32 37 } > !2 = metadata !{ i32 2, metadata !"qux", i32 42 } > !3 = metadata !{ i32 3, metadata !"qux", > metadata !{ > metadata !"foo", i32 1 > } > } > !llvm.module.flags = !{ !0, !1, !2, !3 } > > - Metadata !0 has the ID !"foo" and the value '1'. The beh...

On 05/12/2019 11:00 a.m., Johann R. Kleinbub wrote: > It's been three months without an answer, is it ok to thread bump? > Would someone provide a pointer? I agree it's a bug, and agree with your analysis. You should report it on bugs.r-project.org. (If you don't have an account there, let us know, and either someone will give you one, or someone will report it for you.)

...ing ?fred.R? Comparing ?fred.Rout? to ?fred.Rout.save? ... OK Running ?lpcdd.R? Comparing ?lpcdd.Rout? to ?lpcdd.Rout.save? ... OK Running ?oops.R? Comparing ?oops.Rout? to ?oops.Rout.save? ... OK Running ?qmatmult.R? Comparing ?qmatmult.Rout? to ?qmatmult.Rout.save? ... OK Running ?qux-gmp.R? Comparing ?qux-gmp.Rout? to ?qux-gmp.Rout.save? ... OK Running ?qux.R? Comparing ?qux.Rout? to ?qux.Rout.save? ... OK Running ?redund.R? Comparing ?redund.Rout? to ?redund.Rout.save? ... OK Running ?sammy.R? Comparing ?sammy.Rout? to ?sammy.Rout.save? ... OK Running ?subset.R...

Realized I didn't document the original reviews that motivated this thread: A stack of reviews, split off from here: https://reviews.llvm.org/D69787 Alok's posted a new patch (with smaller patches split off from the monolithic one) here: https://reviews.llvm.org/D84112 I haven't had a chance to page in all the old context, nor look at the new ones in detail yet. But probably worth

On Oct 26, 2007, at 11:12 AM, Bill Wendling wrote: > Hi all, > > The patch below is to fix a problem with unaligned memcpys. This > program: > > void Bork() { > int Qux[33] = {0}; > } > > will currently produce this LLVM code on PPC64: > > @C.0.937 = internal constant [33 x i8] zeroinitializer > > define void @Bork() { > entry: > %Qux = alloca [33 x i8] > %Qux1 = bitcast [33 x i8]* %Qux to i8* > call void @llvm.memcpy.i64...

...e behavior but different values. >>> >>> An example of module flags: >>> >>> !0 = metadata !{ i32 1, metadata !"foo", i32 1 } >>> !1 = metadata !{ i32 4, metadata !"bar", i32 37 } >>> !2 = metadata !{ i32 2, metadata !"qux", i32 42 } >>> !3 = metadata !{ i32 3, metadata !"qux", >>> metadata !{ >>> metadata !"foo", i32 1 >>> } >>> } >>> !llvm.module.flags = !{ !0, !1, !2, !3 } >>> >>> - Metadata !0 has the ID !&qu...

...of the time-series with window<-.ts Consider the following examples of time series with ugly values: x = 1:22 foo = ts(x, start = 1.5, end = 106.5, frequency = 0.2) # a ts of 525 cycles bar = ts(x, start = 2.5, end = 107.5, frequency = 0.2) # a ts of 525 cycles starting 5 cycles later than foo qux = ts(x, start = 2.5, end = 102.5, frequency = 0.2) # a ts of 500 cycles starting 5 cycles later than foo # extraction works fine window(foo, start = 20, end = 30) # works fine window(bar, start = 20, end = 30) # works fine window(qux, start = 20, end = 30) # works fine # assignment fails in di...

Is it more efficient to return void rather than the int 0, e.g. does it reduce register pressure? -- Dr Jon Harrop, Flying Frog Consultancy Ltd. http://www.ffconsultancy.com/?e