search for: analyers

This was an interesting post from another list I'm on. I think that with all of the echo cancellation discussion happening, that someone perhaps might be on the lookout for this type of software, so this post was well-timed for Asterisk uses. It is perhaps the case that those of you working on volume/echo/etc stuff might find this useful towards your goals. JT >To: [snip]

Hi, We are running 1.4.22 and have been experiencing problems with certain IVRs and DTMF Tone duration. We would like to be able to increase DTMF Tone duration by 50 to 100ms over what the user is pressing on his phone. We have a PRI test circuit and an analyer in between to measure tone duration. We have tried setting chan_dahdi.conf parameter 'toneduration', but that does not do

Sorry the 1st example I gave it bit lame, it is changed to following: // a[] is local array, no addr taken. die right after the loop for (i = 0; i < N; i++) { a[i] = ... /* s1 */ sum += a[i-1]; } S1 could be easily deleted if alias analyizer say a[i] and a[i-1]. On 11/8/12 6:07 PM, Shuxin Yang wrote: > Hi, > > In today meeting, Dan gave a very

Hi, In today meeting, Dan gave a very impressive talk about alias analysis. I had a question about the example in his slide, something like: for (i = 0; i < N; i++) a[i] = a[i-1] + 1; For the sake of convenience, let A1, A2 be a[i] and a[i-1] respectively. In Dan's design, Alias(A1, A2) would give "no alias", and in order to prevent A2 from being mistakenly moved out

Hello, I'm afraid I don't understand your question. Could you restate your example and your question, and say what specifically you would like alias analysis to do? Dan On Fri, Nov 9, 2012 at 9:31 AM, Shuxin Yang <shuxin.llvm at gmail.com> wrote: > Sorry the 1st example I gave it bit lame, it is changed to following: > > // a[] is local array, no addr taken. die right

is there any facility in icecast2 to log listner statistics and data usage to xml or json file so i can build reports on top of it? With Best -Ashwin. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/icecast/attachments/20130711/c6ad7828/attachment.htm

Hi, In the following instruction sequence, llvm.objectsize.i64(p) returns 6 (the entire *.ll is attached to the mail). Is this correct? Shouldn't the "object" refer to the entire block of memory being allocated? (char*) p = malloc(56) llvm.objectisize.i32(p+50); Thanks Shuxin This question is related to PR14988 (failure in bootstrap build with LTO). Part of the

>what specifically you would like alias analysis to do? Quite honestly, I don't know what interface is convenient for optimizer. I once implemented a flow-sensitive alias-analysis as a hobby project, which was able to disambiguate the subscripted variables like a[i] and a[i-1]. Unfortunately, the interface is pretty messy, that is why I solicit your insight on this issue. The problem

Hi, Regarding the definition of object for @llvm.objectsize, it is identical to gcc's __builtin_object_size(). So it's not wrong; it's just the way it was defined to be. Regarding the BasicAA's usage of these functions, I'm unsure. It seems to me that isObjectSmallerThan() also expects the same definition, but I didn't review the code carefully. When you do a