Displaying 15 results from an estimated 15 matches for "wave2al".
Did you mean:
wave2all
2008 Apr 15
6
[LLVMdev] PATCH: Use size reduction -- wave2
Hi All,
here comes the patch for the second wave of Use class size reduction.
I have included all the machinery that is needed, and it is
*active*. The User* inside of Use is even sometimes NULL,
but the algorithm is able to recover it.
If there is a non-null User* present, then I am
asserting that it equals the computed value.
I did not receive feedback for the algorithmic part yet,
so I
2008 Apr 16
0
[LLVMdev] PATCH: Use size reduction -- wave2
Hi Gabor,
Can you provide performance data for this? I'd
like to know what affect these changes have on
compile time.
Thanks,
Dan
On Apr 15, 2008, at 3:32 PM, Gabor Greif wrote:
> Hi All,
>
> here comes the patch for the second wave of Use class size reduction.
>
> I have included all the machinery that is needed, and it is
> *active*. The User* inside of Use is even
2008 Apr 17
0
[LLVMdev] PATCH: Use size reduction -- wave2
Gabor,
Have you updated llvm2cpp to generate calls to the appropriate new
constructors? Also, could you check the code in the tutorials to make
sure it matches the new API?
--Owen
On Apr 15, 2008, at 5:32 PM, Gabor Greif wrote:
> Hi All,
>
> here comes the patch for the second wave of Use class size reduction.
>
> I have included all the machinery that is needed, and it is
2008 Apr 16
0
[LLVMdev] PATCH: Use size reduction -- wave2
> Unfortunately I had to introduce a new GlobalVariable::Create
> mechanism (I hoped to have nailed all in wave 1, but life is cruel).
> I will submit scripts for the easy conversion of external projects
> like the last time.
One request is to explicity explain the new mechanism so people don't have
to read the diffs or extrapolate from the conversion scripts.
Please send a
2008 Apr 16
5
[LLVMdev] PATCH: Use size reduction -- wave2
On Apr 16, 2:13 am, Dan Gohman <goh... at apple.com> wrote:
> Hi Gabor,
>
> Can you provide performance data for this? I'd
> like to know what affect these changes have on
> compile time.
Hi Dan,
Unfortunately, no. I can feed you with some speculation, though,
see below.
The reason why I cannot do measurements (at the moment) is that
- I have no experience with
2008 Apr 16
1
[LLVMdev] PATCH: Use size reduction -- wave2
On Apr 16, 2:42 am, "Tanya M. Lattner" <to... at nondot.org> wrote:
> > Unfortunately I had to introduce a new GlobalVariable::Create
> > mechanism (I hoped to have nailed all in wave 1, but life is cruel).
> > I will submit scripts for the easy conversion of external projects
> > like the last time.
>
> One request is to explicity explain the new
2008 Apr 18
2
[LLVMdev] PATCH: Use size reduction -- wave2
On Apr 17, 7:01 pm, Owen Anderson <resis... at mac.com> wrote:
> Gabor,
>
> Have you updated llvm2cpp to generate calls to the appropriate new
Yes. These are caught by my conversion scripts.
> constructors? Also, could you check the code in the tutorials to make
> sure it matches the new API?
Good point, will do.
Thanks,
Gabor
>
> --Owen
2008 Apr 19
0
[LLVMdev] PATCH: Use size reduction -- wave2
On Apr 18, 5:51 pm, heisenbug <ggr... at gmail.com> wrote:
> On Apr 17, 7:01 pm, Owen Anderson <resis... at mac.com> wrote:
>
> > Gabor,
>
> > Have you updated llvm2cpp to generate calls to the appropriate new
>
> Yes. These are caught by my conversion scripts.
>
> > constructors? Also, could you check the code in the tutorials to make
> >
2008 Apr 23
0
[LLVMdev] PATCH: Use size reduction -- wave2
On Apr 17, 4:12 am, Chris Lattner <sa... at nondot.org> wrote:
> On Apr 16, 2008, at 11:25 AM, Dan Gohman wrote:
>
> >> So, my idea is that these changes are performance neutral.
>
> I strongly agree with Dan that we need to measure performance to
> ensure there is no significant performance regression.
Dan, Chris,
finally I am in possession of hard performance data
2008 Apr 17
2
[LLVMdev] PATCH: Use size reduction -- wave2
On Apr 16, 2008, at 11:25 AM, Dan Gohman wrote:
>> So, my idea is that these changes are performance neutral.
I strongly agree with Dan that we need to measure performance to
ensure there is no significant performance regression.
>> I hope that this is interesting, but I'd like to ask anybody who is
>> comfortable with performance testing to help provide some hard
2008 Apr 16
0
[LLVMdev] PATCH: Use size reduction -- wave2
On Apr 16, 2008, at 2:50 AM, heisenbug wrote:
>
> And now here is my educated speculation:
> There are 2 things that became slower
> 1) Use::getUser()
> 2) Use::get/set due to tagging.
>
> The former is seldom called:
>
> $ find lib -name "*.cpp" | xargs grep "getUser(" | wc -l
> 41
The majority of those aren't actually Use::getUser, but
2005 Sep 18
5
Monitor and sox mix quality
Hello All,
I am using monitor with soxmix, however the quality seems somewhat low
after sox converts to mp3.
Does anyone know a way to get a higher quality file? Some of my lines
are coming in on isdn.
Regards,
Greg
2008 Jan 14
1
Asterisk 1.4 Call Recording
I am trying to record a call into a stereo mp3 in Asterisk 1.4, but I can't seem to get it to work correct. Could someone point me to what I need to do? I have attached what I believe are the relevant parts.
[globals]
; script to be executed when monitoring has been finished
MONITOR_EXEC=/usr/local/bin/2wav2mp3
; uncomment this line if you are using Ogg Vorbis
2012 Aug 21
2
Iterative sampling with restrictions
Hi all,
I'm working on a seemingly trivial problem that I can't figure out how
to implement in R. I'd be most grateful for any help here.
I want to do the following: first, randomly assign each of n units to
one of g groups of size n/g. Then, randomly re-assign each of the n
units to a different group (i.e., same as the first step, but the unit
can't be assigned to a group to
2006 Feb 10
1
2wav2mp3, monitor, mixmonitor, mpg123, queues
Hello!
I'm using Asterisk for our office telephony, but we have some problems
that still we can't resolve about it. Here they are:
1) merge in/out call recording files
I also tried to use a script I found on the internet, called 2wav2mp3
In extensions.conf I added the following lines
; script to be executed when monitoring has been finished
MONITOR_EXEC=/usr/local/bin/2wav2mp3
exten