search for: lsl

...ic value but a vector of two elements using return(c(val1, val2)). I don't know how to access the individual columns of that vector in the resulting dataframe though. How is this done correctly? Thanks, robert > agg <- aggregate(formula=df$value ~ df$quarter + df$tool, + FUN=cp.cpk, lsl=1300, usl=1500) > head(agg) df$quarter df$tool df$value 1 09Q3 VS1A 1.800534, 1.628483 2 10Q1 VS1A 1.299652, 1.261302 3 10Q2 VS1A 1.699018, 1.381570 4 10Q3 VS1A 1.311681, 1.067232 > head(agg["df$value"]) df$value 1 1.800534...

...ter in this patch, this change in the docs and example code implies the use of the REQUIRE_TLS flag. Is that intentional that passing all flags forbids the use of non-encrypted connections? > +++ b/generator/generator > @@ -939,7 +939,17 @@ let cmd_flags = { > "REQ_ONE", 1 lsl 3; > ] > } > -let all_flags = [ cmd_flags ] > +let connect_uri_allow_flags = { > + flag_prefix = "CONNECT_URI"; > + all_flags_bitmask = true; > + flags = [ > + "ALLOW_TCP", 1 lsl 0; > + "ALLOW_UNIX", 1 lsl 1; > + "A...

...ecific_integral is fairly efficient. For example, on x86_64 reading 32 bits with 1 2 and 4 byte alignment produces in all cases: movl (%rdi), %eax But on armv6 the aligned case is ldr r0, [r0] the 2 byte aligned case is ldrh r1, [r0, #2] ldrh r0, [r0] orr r0, r0, r1, lsl #16 and the unaligned case is ldrb r1, [r0] ldrb r2, [r0, #1] ldrb r3, [r0, #2] ldrb r0, [r0, #3] orr r1, r1, r2, lsl #8 orr r0, r3, r0, lsl #8 orr r0, r1, r0, lsl #16 On armv7 it is a single ldr on all cases. Now, I don't really know how much we suppor...

...ing at some AArch64 benchmarks and noticed some simple cases where addresses are being folded into the address mode computations and was curious as to why. In particular, consider the following simple example: void f2(unsigned long *x, unsigned long c) { x[c] *= 2; } This generates: lsl x8, x1, #3 ldr x9, [x0, x8] lsl x9, x9, #1 str x9, [x0, x8] Given the two uses of the address computation I was expecting this: add x8, x0, x1, lsl #3 ldr x9, [x8] lsl x9, x9, #1 str x9, [x8] >From reading 'SelectAddrModeXRO' the computation is getting folded if the add...

...ROTOCOL_H */ diff --git a/generator/generator b/generator/generator index c509573..9b1f5d8 100755 --- a/generator/generator +++ b/generator/generator @@ -958,10 +958,11 @@ let all_enums = [ tls_enum ] let cmd_flags = { flag_prefix = "CMD_FLAG"; flags = [ - "FUA", 1 lsl 0; - "NO_HOLE", 1 lsl 1; - "DF", 1 lsl 2; - "REQ_ONE", 1 lsl 3; + "FUA", 1 lsl 0; + "NO_HOLE", 1 lsl 1; + "DF", 1 lsl 2; + "REQ_ONE", 1 lsl 3; + "FAST_ZERO", 1 lsl 4; ]...

...y first candidate was switch-case lowering. I also created a Bugzilla issue for this topic: https://bugs.llvm.org/show_bug.cgi?id=34902 The full example code and the generated assembly for GCC and for LLVM is in the Bugzilla issue. My first idea was to simplify the following instruction pattern *lsl     r0, r0, #2** **       ldr     pc, [r0, r1]* to this: *ldr     pc, [r1, r0, lsl #2]* but then I got really confused when I started to look into the machine-dependent optimization passes in the backend. I get a dump with the '-print-machineinstrs' option from the MachineFunctionPass a...

...gt; LBB1_1: > ldrsh r3, [r1] # loads a short that is sign-extended to 32 bits > mov r4, lr > cmp r3, #2048 > bge .LBB1_3 > and r4, r3, r12 # mask with 0xffff to convert to short again > lsl r4, r4, #16 # this lsl and the following > asr r5, r4, #16 # asr implement sign-extension to 32 bits again .... > ldr r4, .LCPI1_1 > cmn r5, #2048 > movge r4, r3 > .LBB1_3: > str r4, [r2, r0,...

...er_mem2 bit exact with the C. -Fritz -------------- next part -------------- --- filters_arm4.h 2005-11-16 06:08:28.000000000 -0500 +++ filters_arm4_new.h 2005-12-06 11:06:51.012221200 -0500 @@ -240,9 +240,11 @@ "\tmov %8, %8, lsr #15\n" "\tadd %10, %8, %9, lsl #17\n" "\tldrsh %6, [%2], #2\n" - "\tsmull %8, %9, %5, %6\n" - "\tadd %10, %10, %8, lsr #15\n" - "\tadd %10, %10, %9, lsl #17\n" + "\trsb %11, %5, #0\n" + "\tsmull %8, %9,...

...165,6 +166,7 @@ let all_enums = [ tls_enum; block_size_enum ] (* Flags. See also Constants below. *) let cmd_flags = { flag_prefix = "CMD_FLAG"; + guard = Some "((h->strict & LIBNBD_STRICT_FLAGS) || flags > UINT16_MAX)"; flags = [ "FUA", 1 lsl 0; "NO_HOLE", 1 lsl 1; @@ -175,6 +177,7 @@ let cmd_flags = { } let handshake_flags = { flag_prefix = "HANDSHAKE_FLAG"; + guard = None; flags = [ "FIXED_NEWSTYLE", 1 lsl 0; "NO_ZEROES", 1 lsl 1; @@ -182,12 +185,15 @@ let handshak...

Hi I know this subject has been mentioned before but from the mail archives I'm under the impression that this is not possible ? I'm trying to carryout the equivalent of ls -l in R to give some date/time label to each of my objects If the case is that there is no equivalent, is it possible to list all objects in an environment that share a common component ? So that the common

...14, r5 @ Clip positive cmn r14, r5 rsblt r14, r5, #0 @ Clip negative strh r14, [r2], #2 @ Write result to y[i] rsb r14, r14, #0 @ r14 = -y[i] ldmia r1!, { r10-r12 } @ r10-r12 = den[0..5] mov r5, r10, lsl #16 mov r5, r5, asr #16 mla r5, r14, r5, r6 @ mem[0] = mem[1] - den[0]*y[i] mov r10, r10, asr #16 mla r6, r14, r10, r7 @ mem[1] = mem[2] - den[1]*y[i] mov r10, r11, lsl #16 mov r10, r10, asr #16 mla r7, r14, r10, r8 @ mem...

...ode > implies the use of the REQUIRE_TLS flag. Is that intentional that > passing all flags forbids the use of non-encrypted connections? Yes I believe it's wrong. > > +++ b/generator/generator > > @@ -939,7 +939,17 @@ let cmd_flags = { > > "REQ_ONE", 1 lsl 3; > > ] > > } > > -let all_flags = [ cmd_flags ] > > +let connect_uri_allow_flags = { > > + flag_prefix = "CONNECT_URI"; > > + all_flags_bitmask = true; > > + flags = [ > > + "ALLOW_TCP", 1 lsl 0; > > + "...

...= [ tls_enum; block_size_enum ] > (* Flags. See also Constants below. *) > let cmd_flags = { > flag_prefix = "CMD_FLAG"; > + guard = Some "((h->strict & LIBNBD_STRICT_FLAGS) || flags > UINT16_MAX)"; > flags = [ > "FUA", 1 lsl 0; > "NO_HOLE", 1 lsl 1; > @@ -175,6 +177,7 @@ let cmd_flags = { > } > let handshake_flags = { > flag_prefix = "HANDSHAKE_FLAG"; > + guard = None; > flags = [ > "FIXED_NEWSTYLE", 1 lsl 0; > "NO_ZEROES",...

...iple +packets would otherwise allow a more efficient representation of +holes contained in the region (if that is supported - some servers +cannot do this, see C<nbd_can_df>)."; }; "pwrite", { @@ -1774,6 +1790,7 @@ let constants = [ "CMD_FLAG_FUA", 1 lsl 0; "CMD_FLAG_NO_HOLE", 1 lsl 1; + "CMD_FLAG_DF", 1 lsl 2; "CMD_FLAG_REQ_ONE", 1 lsl 3; ] diff --git a/lib/flags.c b/lib/flags.c index 421a7d2..cdbc28f 100644 --- a/lib/flags.c +++ b/lib/flags.c @@ -42,6 +42,11 @@ nbd_internal_set_size_and_flags (...

Martin Richtarsky <s at martinien.de> writes: > Output looks as follows [1] Seems sh_offset is missing? That is what readelf prints as Off > [17] .rela.text RELA 0000000000000000 071423 001728 18 > 1 4 8 The offset of rela text should have been aligned, but it is not. Can you report a bug on icc? As a work around using the gnu assembler if possible

...08d68 in main () (gdb) disassemble Dump of assembler code for function open_loop_nbest_pitch: ... skipped... 0x40030300 <open_loop_nbest_pitch+620>: add r0, r3, r8 0x40030304 <open_loop_nbest_pitch+624>: ldrsh r3, [r0] 0x40030308 <open_loop_nbest_pitch+628>: mov r3, r3, lsl #1 0x4003030c <open_loop_nbest_pitch+632>: strh r3, [r0], #2 0x40030310 <open_loop_nbest_pitch+636>: add r6, r6, #1 ; 0x1 0x40030314 <open_loop_nbest_pitch+640>: cmp r6, r7 0x40030318 <open_loop_nbest_pitch+644>: bne 0x40030304 <open_loop_nbest_pitch+6...

Hi, I'm trying to get speex working on an ARM board (ARM926EJ-Sid(wb) core, ARM 5TE architecture) and getting segfaults if build with "--enable-fixed-point --enable-arm5e-asm" options. If I use just "--enable-fixed-point", then it runs fine, but once I add "--enable-arm5e-asm" it start crashing (I use testenc to test it). Further investigation showed, that it

...'t know how to do that because I don't know beforehand how many series I create in the for() loop, how to distinguish them by (unknown beforehand) tool names, and how to supply them to ts.union. Thanks, robert ############################ CODE HERE library(zoo) ppk <- function(data, lsl, usl) { if (length(data) < 15) { return(NA) } else { return (min(mean(data)-lsl, usl-mean(data))/(3*sd(data))) } } load <- function(filename) { d <- read.table(filename, header=TRUE, sep='\t') # filter data d <- d[...

...ackend. As a warmup exercise I wanted to be able to move jumptables especially large ones out of the code section. Currently the idiom for jump tables loooks like this // .set PCRELV0, (.LJTI9_0_0-(.LPCRELL0+8)) // .LPCRELL0: // add r3, pc, #PCRELV0 // ldr pc, [r3, +r0, lsl #2] // .LJTI9_0_0: // .long .LBB9_2 // .long .LBB9_5 // .long .LBB9_7 // .long .LBB9_4 // .long .LBB9_8 I would like to be able to change this to something like: ldr r3, .POOL_ADDR ldr pc, [r3, +r0, lsl #2 .POOL...

...fprintf (stderr, "%s\n", nbd_get_error ()); exit (EXIT_FAILURE); } diff --git a/generator/generator b/generator/generator index fe24738..5f5523a 100755 --- a/generator/generator +++ b/generator/generator @@ -939,7 +939,17 @@ let cmd_flags = { "REQ_ONE", 1 lsl 3; ] } -let all_flags = [ cmd_flags ] +let connect_uri_allow_flags = { + flag_prefix = "CONNECT_URI"; + all_flags_bitmask = true; + flags = [ + "ALLOW_TCP", 1 lsl 0; + "ALLOW_UNIX", 1 lsl 1; + "ALLOW_TLS", 1 lsl 2; + "REQUIRE_TLS&...