search for: q13

...0.0e+00 Q7 <--- G param9 0.60 0.059 10.1 0.0e+00 Q9 <--- G param10 0.64 0.065 9.9 0.0e+00 Q10 <--- G param11 0.72 0.054 13.3 0.0e+00 Q11 <--- G param12 0.59 0.063 9.3 0.0e+00 Q12 <--- G param13 0.61 0.069 8.7 0.0e+00 Q13 <--- G param14 0.70 0.074 9.6 0.0e+00 Q14 <--- G param15 0.68 0.066 10.4 0.0e+00 Q15 <--- G param16 0.75 0.056 13.3 0.0e+00 Q16 <--- G param17 0.86 0.060 14.3 0.0e+00 Q17 <--- G param18 0.63 0.059 10.7 0.0e+00 Q18 <--- G...

Hi all, On following code when I use llc targeting ARM Cortex-A9 as follows, if vmlx-forwarding is turned off then 'vmla' instructions are generated. It seems that -mcpu=cortex-a9 enables it by default and thus less 'vmla' instructions are generated. On this specific example it doesn't make any difference in term of performance, but on a more complex example disabling

...elow: Lastname Firstname CATALOG_NBR Email StudentID EMPLID Start 1 alastname afirstname 1213 *@uark.edu 10295236 # 12/2/2008 2 anotherlastname anotherfirstname 1213 **@uark.edu ## 10295236 9/3/2008 Xattempts Q1 Q2 Q3 Q4 Q5 Q6 Q7 Q8 Q9 Q10 Q11 Q12 Q13 Q14 Q15 Q16 Q17 Q18 Q19 1 1 1 1 0 0 0 0 0 0 0 1 0 0 1 1 0 1 1 0 1 2 1 1 1 1 1 1 0 1 0 0 1 1 0 0 1 0 0 0 0 1 Q20 Q21 Q22 Q23 Q24 Q25 Q26 Q27 Q28 Q29 Q30 Q31 Q32 Score Form CRSE_GRADE_OFF 1 0 0 0 0 0 0 0 0 0...

...iterations for epilogue loop to 14 test.c:11: note: LOOP VECTORIZED. The result is a very concise and very dense code: vld1.8 {d28[], d29[]}, [r5] vld3.8 {d16, d18, d20}, [r9]! vld3.8 {d17, d19, d21}, [r9] vmvn q3, q8 vmvn q15, q9 vmvn q8, q10 vsub.i8 q11, q3, q14 vsub.i8 q12, q15, q14 vsub.i8 q13, q8, q14 vst3.8 {d22, d24, d26}, [r8]! vst3.8 {d23, d25, d27}, [r8] cheers, --renato -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131014/a05ed9f0/attachment.html> -------------- next part -------------...

...e states<-structure(states$PC, names=states$Species) names(states)<-tree$tip.label #MuSSE diversitree:::argnames.musse(NULL, 3) #number of states lik<-make.musse(tree, states, 3) argnames(lik) #contstrain lambda lik.base<-constrain(lik, lambda2~lambda1, lambda3~lambda1, mu2~mu1,mu3~mu1,q13~q12,q21~q12,q23~q12,q31~q12,q32~q12) #find ML point for this model p<-starting.point.musse(tree, 3) fit.base<-find.mle(lik.base, p[argnames(lik.base)]) #unconstrained lik.lambda<-constrain(lik,mu2~mu1,mu3~mu1,q13~q12,q21~q12,q23~q12,q31~q12,q32~q12) fit.lambda<-find.mle(lik.lambda, p[a...

I have end of semester teaching evaluation data of the following form: > head(evaluations) Course Prefix Q1 Q2 Q3 Q4 Q5 Q6 Q7 Q8 Q9 Q10 Q11 Q12 Q13 Q14 1 2330301 2 4 3 3 3 4 4 1 2 5 4 1 1 1 1 2 2330301 2 3 3 3 3 3 5 1 2 5 8 1 1 1 1 3 2330301 2 4 4 3 3 4 4 2 2 5 9 1 1 1 1 4 2330301 2 2 1 1 3 4 5 1 2 5 8 1 1 1 1 5 2330301 2 4 3 4 4 4 3 1...

...example, Q1 in one of my data frames has over 66% of its observations missing. I have tried imputation with mice but it does not work for all the data frames and I get the following message or a similar message to this: iter imp variable 1 1 Q1 Q2 Q3 Q4 Q5 Q6 Q7 Q8 Q9 Q10 Q11 Q12 Q13 Q14 Q15 Q19 Q36 Q47 Q52 Q79 Q80 Q94 Q97 Q104 Q108 Q122 Q131 Q134 P1 P2 P3 P4 P5 P6Error in solve.default(xtx + diag(pen)) : system is computationally singular: reciprocal condition number = 1.83044e-16 In addition: Warning messages: 1: In sqrt((sum(residuals^2))/(sum(ry) - n...

Mathias Gygax wrote: >On Son, Jan 05, 2003 at 08:24:45 +0100, tcheer@gmx.de wrote: > > >>Hi all, >> >> > >hi there, > Hi again... > > > >>1. >>I have just installed ices 0.2.3 and icecast 1.3.12 and I am trying to >>run them. >>In my etc/icecast.const i have kept the 3 default passwords for the >>encoder, admin

...e password configurations (e.g. encoder_password) > >in icecast.conf. it should work then. > > OK I did so and pasted the result (icxDriEO6Fgt.) in the icecast.conf > file (and later in both icecast.conf and ices.conf) entries, but the > error remains.... :-( according to FAQ: Q13: What's the story with crypted passwords? A13: Normally, icecast and shoutcast servers keep the passwords uncrypted, either in a configfile, or specified on the command line. This is pretty poor security. Newer versions of icecast provide a configuration option (--with-crypt). Wi...

Hi Jean-Marc, I'm currently trying to analyze the LPC synthesis filter. For this, can you please tell me the exact format of the LPC coeffs (in variable interp_qlpc), please? cheers, Frank -----Urspr?ngliche Nachricht----- Von: "Frank Lorenz" <Frank_wtal at web.de> Gesendet: 02.02.10 11:00:16 An: jean-marc.valin at usherbrooke.ca CC: speex-dev at xiph.org Betreff: Re:

On 21 September 2012 09:28, Sebastien DELDON-GNB <sebastien.deldon at st.com> wrote: > declare <16 x float> @llvm.arm.neon.vmaxs.v16f32(<16 x float>, <16 x float>) nounwind readnone > > llc fails with following message: > > SplitVectorResult #0: 0x2258350: v16f32 = llvm.arm.neon.vmaxs 0x2258250, 0x2258050, 0x2258150 [ORD=3] [ID=0] > > LLVM ERROR: Do not

R Experts, I have a dataframe made up of character vectors--these are results from survey questions. I need to convert them to factors. I tried the following which did not work: scs2<-sapply(scs2,as.factor) also this didn't work: scs2<-sapply(scs2,function(x) as.factor(x)) After doing either of above I end up with >str(scs2) chr [1:10, 1:10] "very important" "very

Renato, can you post the c code for the function and the assembly that gcc produces? Your initial example could be well handled by vectorization of strided loops (and the mentioning of VLD3(.8?)/VST3(.8?) lead me to assume that this is what happened). But the LLVM-IR you sent has a store of 0 in there ;) and strides by 4. Thanks, Arnold Vectorization of strided loops: I am using float as the

...vld1.64 {d20, d21}, [r3, :128] add r3, r2, #48 vld1.64 {d16, d17}, [r2, :128] add r2, r2, #16 vld1.64 {d18, d19}, [r1, :128] vld1.64 {d26, d27}, [r12, :128] add r12, r1, #32 vld1.64 {d24, d25}, [r3, :128] add r1, r1, #16 vadd.f32 q11, q9, q8 vld1.64 {d28, d29}, [r12, :128] vadd.f32 q9, q13, q12 vadd.f32 q8, q14, q10 vld1.64 {d20, d21}, [r2, :128] vld1.64 {d24, d25}, [r1, :128] add r1, r0, #48 vadd.f32 q10, q12, q10 vst1.64 {d22, d23}, [r0, :128] vst1.64 {d18, d19}, [r1, :128] add r1, r0, #32 add r0, r0, #16 vst1.64 {d16, d17}, [r1, :128] vst1.64 {d20, d21}, [r0, :128] bx...

...-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEj2Yw899ysxFmsp8RArgrAJwLYHCy0vf5m6/iAQwtt+/+pOFPWACg/Q13 6xkVN0cpZjeKAeGWj7qKdOM= =hv4P -----END PGP SIGNATURE----- --------------enig807B2312A20EAF60129FDDFA--

This is almost ideal for SLP vectorization, except for two problems: 1. We have 4 stores to consecutive locations, but the last element is the constant zero, and not an additional SUB. At the moment we don’t have support for idempotence operations, but this is something that we should add. 2. The values that we are subtracting come from 3 loads. We usually load 4 elements from memory, or

...quot;, "o9", "ox", "p10", "p11", "p2", "p3", "p4", "p5", "p6", "p7", "p8", "p9", "px", "q1", "q10", "q11", "q12", "q13", "q2", "q3", "q4", "q5", "q6", "q7", "q8", "q9", "qx", "r1", "r10", "r11", "r12", "r13", "r14", "r15", "r2", &quo...

...ulse signal */ + const opus_int16 PredCoef_Q12[ 2 * MAX_LPC_ORDER ], /* I Short term prediction coefs */ + const opus_int16 LTPCoef_Q14[ LTP_ORDER * MAX_NB_SUBFR ], /* I Long term prediction coefs */ + const opus_int16 AR_Q13[ MAX_NB_SUBFR * MAX_SHAPE_LPC_ORDER ], /* I Noise shaping coefs */ + const opus_int HarmShapeGain_Q14[ MAX_NB_SUBFR ], /* I Long term shaping coefs */ + const opus_int Tilt_Q14[ MAX_NB_SUBFR ], /* I Spectral tilt...

NSQ_LPC_BUF_LENGTH is independent of DECISION_DELAY. --- silk/define.h | 4 ---- 1 file changed, 4 deletions(-) diff --git a/silk/define.h b/silk/define.h index 781cfdc..1286048 100644 --- a/silk/define.h +++ b/silk/define.h @@ -173,11 +173,7 @@ extern "C" #define MAX_MATRIX_SIZE MAX_LPC_ORDER /* Max of LPC Order and LTP order */ -#if( MAX_LPC_ORDER >

Hi all, I would like to know if LLVM Neon intrinsics are designed to support only 'Legal' types for NEON units. Using llc -march=arm -mcpu=cortex-a9 vmax4.ll -o vmax4.s on following ll code: ; ModuleID = 'vmax.ll' target datalayout = "e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v64:64:64-v128:128:128-a0:0:64-n32" target triple =