Displaying 5 results from an estimated 5 matches for "get_p".
Did you mean:
get_dp
2006 Nov 15
1
Quick survey for Speex 1.2
...se. This really helped users to
> improve the quality of their input, as they could clearly and
> immediately see the effect of changes in the environment.
> These data are now private and can't easily be extracted from an outside
> program. Would it be possible to add _ctl calls to GET_PS, GET_NOISE,
> GET_SNR etc? Would you accept patches which did this?
One of the main reasons the struct is now private is that its content
depends on whether Speex was compiled for fixed-point or floating-point.
I'm not against making it possible to extract some information, but it
needs t...
2018 May 24
0
LLVM SEH docs -- enregistration of locals in nonvolatile registers?
Is this example what you had in mind?
void f() {
int *p = get_p();
use_p(p);
try {
may_throw(p);
} catch (int) {
// don't need p
}
use_p(p);
}
The idea is that because p is not modified or used within the catch region
(the funclet), it can live in a callee-saved register across the whole
function.
That is true, it is possible, but I don...
2018 May 22
2
LLVM SEH docs -- enregistration of locals in nonvolatile registers?
https://llvm.org/docs/ExceptionHandling.html#wineh
> No variables live in to or out of the funclet can be allocated in registers.
I don't think this is quite true. though it might be a useful simplification.
Obviously it is true for volatile registers, but I believe the funclet receives a CONTEXT
with the nonvolatiles restored. Obviously cumbersome to access, but it lets you enregister
2006 Nov 15
0
Quick survey for Speex 1.2
...iew of ps and noise. This really helped users to
improve the quality of their input, as they could clearly and
immediately see the effect of changes in the environment.
These data are now private and can't easily be extracted from an outside
program. Would it be possible to add _ctl calls to GET_PS, GET_NOISE,
GET_SNR etc? Would you accept patches which did this?
2006 Nov 13
13
Quick survey for Speex 1.2
Hi everyone,
As you may have guess, Speex 1.2 is slowly approaching, though there's
still a lot left to do so I can't say how long it'll take. I thought
this was the right time to ask if there's anything missing or that can
be improved to make 1.2 better. At this point, it can't be anything
major, but there are still some changes that are possible, e.g:
- Improving some