search for: wtmp2

...ot;kiss_fft.c", line 142: warning: shift count is too large > > > I've noticed this on the echo canceller and the preprocessor. all > pretty much related to these two lines of code: > > kiss_fft > C_MUL4(scratch[0],Fout[m] , *tw1 ); > > mdf.c > st->wtmp2[i] = EXTRACT16(PSHR32(st->W[j*N+i],NORMALIZE_SCALEDOWN+16)); > > Is there some kind of switch I was supposed to throw to not get these > messages? if not-are they hurting anything? > > -Mike > > > > ---------------------------------------------------------------...

...-ubBwr clean/libspeex/mdf.c impulse_scale/libspeex/mdf.c --- clean/libspeex/mdf.c 2008-02-13 11:12:13.000000000 +0100 +++ impulse_scale/libspeex/mdf.c 2008-02-13 22:47:44.000000000 +0100 @@ -1180,13 +1180,13 @@ { #ifdef FIXED_POINT for (i=0;i<N;i++) - st->wtmp2[i] = EXTRACT16(PSHR32(st->W[j*N+i],16)); + st->wtmp2[i] = EXTRACT16(PSHR32(st->W[j*N+i],16+NORMALIZE_SCALEDOWN)); spx_ifft(st->fft_table, st->wtmp2, st->wtmp); #else spx_ifft(st->fft_table, &st->W[j*N], st->wtmp); #endif...

...same compiler warnings, and sent a message to the > list which included this: > > "I got several compiler warnings for "shift out of range" in mdf.c, > which I fixed by adding EXTEND32 to all of the SHL32s with 16 bit > operands (st->frame_size in 6 places, st->wtmp2 in 1 place)." Yes, I remember those and I'm pretty sure they're fixed now. I think the problem comes from other changes I made later on, but I can't understand what's wrong. > I sent a patch with some fixes later that month, but I have not built > the echo canceller sin...

...sage to the >>> list which included this: >>> >>> "I got several compiler warnings for "shift out of range" in mdf.c, >>> which I fixed by adding EXTEND32 to all of the SHL32s with 16 bit >>> operands (st->frame_size in 6 places, st->wtmp2 in 1 place)." >> >> Yes, I remember those and I'm pretty sure they're fixed now. I think the >> problem comes from other changes I made later on, but I can't understand >> what's wrong. >> >>> I sent a patch with some fixes later that mont...

...I have been getting warning messages that say: "kiss_fft.c", line 142: warning: shift count is too large I've noticed this on the echo canceller and the preprocessor. all pretty much related to these two lines of code: kiss_fft C_MUL4(scratch[0],Fout[m] , *tw1 ); mdf.c st->wtmp2[i] = EXTRACT16(PSHR32(st->W[j*N+i],NORMALIZE_SCALEDOWN+16)); Is there some kind of switch I was supposed to throw to not get these messages? if not-are they hurting anything? -Mike -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail...

...= st->M * st->frame_size; + break; + case SPEEX_ECHO_GET_IMPULSE_RESPONSE: + { + int M = st->M, N = st->window_size, n = st->frame_size, i, j; + spx_int32_t *filt = (spx_int32_t *) ptr; + for(j=0;j<M;j++) + { +#ifdef FIXED_POINT + for (i=0;i<N;i++) + st->wtmp2[i] = EXTRACT16(PSHR32(st->W[j*N+i],16)); + spx_ifft(st->fft_table, st->wtmp2, st->wtmp); +#else + spx_ifft(st->fft_table, &st->W[j*N], st->wtmp); +#endif + for(i=0;i<n;i++) + filt[j*n+i] = PSHR32(MULT16_16(32767,st->wtmp[i]), WEIGHT_SHIFT); + } + } + break;...

...ast # 1GB / ( 10MB/sec ) ~ 102 seconds ~ One Minute and 42 Seconds. # BTW, the hash algorithm works best if the number of al-extents # is prime. (To test the worst case performace use a power of 2) al-extents 257; } on teddy { device /dev/drbd0; disk /dev/sysb/wtmp2; address 192.168.5.20:7788; meta-disk internal; # meta-disk is either ''internal'' or ''/dev/ice/name [idx]'' # # You can use a single block device to store meta-data # of multiple DRBD''s. # E.g. use meta-disk /dev/hde6[0]; a...

...in May 2006. I got the same compiler warnings, and sent a message to the list which included this: "I got several compiler warnings for "shift out of range" in mdf.c, which I fixed by adding EXTEND32 to all of the SHL32s with 16 bit operands (st->frame_size in 6 places, st->wtmp2 in 1 place)." I sent a patch with some fixes later that month, but I have not built the echo canceller since then (no room for it). It is very likely that you are seeing the same issue, and the fix should be the same also. The trickier problems are the ones that the compiler does not find....

...ich included this: >>>>> >>>>> "I got several compiler warnings for "shift out of range" in mdf.c, >>>>> which I fixed by adding EXTEND32 to all of the SHL32s with 16 bit >>>>> operands (st->frame_size in 6 places, st->wtmp2 in 1 place)." >>>> >>>> Yes, I remember those and I'm pretty sure they're fixed now. I think >>>> the >>>> problem comes from other changes I made later on, but I can't >>>> understand >>>> what's wrong. &g...

...ings, and sent a message to the >> list which included this: >> >> "I got several compiler warnings for "shift out of range" in mdf.c, >> which I fixed by adding EXTEND32 to all of the SHL32s with 16 bit >> operands (st->frame_size in 6 places, st->wtmp2 in 1 place)." > > Yes, I remember those and I'm pretty sure they're fixed now. I think the > problem comes from other changes I made later on, but I can't understand > what's wrong. > >> I sent a patch with some fixes later that month, but I have not built...

...>> list which included this: >>>> >>>> "I got several compiler warnings for "shift out of range" in mdf.c, >>>> which I fixed by adding EXTEND32 to all of the SHL32s with 16 bit >>>> operands (st->frame_size in 6 places, st->wtmp2 in 1 place)." >>> >>> Yes, I remember those and I'm pretty sure they're fixed now. I think the >>> problem comes from other changes I made later on, but I can't understand >>> what's wrong. >>> >>>> I sent a patch with so...

...gt; there were four left that I had to break apart. I started with build > 11343. > > I got several compiler warnings for "shift out of range" in mdf.c, which I > fixed by adding EXTEND32 to all of the SHL32s with 16 bit operands > (st->frame_size in 6 places, st->wtmp2 in 1 place). I have not sent > patches for these two changes, because I still have other problems. > > If fftwrap.c, I ifdefed out the spx_fft_float and spx_ifft_float routines, > because there were not used and required smallft.c (which is not so small > at all) to be added to t...

...atch by Brian Retford), but there were four left that I had to break apart. I started with build 11343. I got several compiler warnings for "shift out of range" in mdf.c, which I fixed by adding EXTEND32 to all of the SHL32s with 16 bit operands (st->frame_size in 6 places, st->wtmp2 in 1 place). I have not sent patches for these two changes, because I still have other problems. If fftwrap.c, I ifdefed out the spx_fft_float and spx_ifft_float routines, because there were not used and required smallft.c (which is not so small at all) to be added to the build. With these ch...

Full_Name: Partho Bhowmick Version: 2.8.1 OS: Windows XP Submission from: (NULL) (199.43.48.131) While trying to install package sn (I have tried multiple mirrors), I get the following message trying URL 'http://www.revolution-computing.com/cran/bin/windows/contrib/2.8/sn_0.4-10.zip' Content type 'application/zip' length 320643 bytes (313 Kb) opened URL downloaded 313 Kb

Hi Ted, Thanks a lot for this analysis. > In FLOAT_DIVU() it hangs at the following: > while (a.m >= b.m) > { > e++; > a.m >>= 1; > } > for the case where a and b are both zero (yes, division by zero). > This happens from mdf.c: True, that needs to be fixed even after I fix the rest. > leak_estimate =