similar to: stack + heap sizes

? There seems to be a memory violation when calling celt_mode_create(48000, 240). ? The function compute_pulse_cache() calls celt_alloc (the second one, bits=celt_alloc()) in order to allocate 343 byte, but it is using about 872 bytes at that location, which will be deleted by the following allocations. ? In this case the following encoder call crashes at first run. ? Sorry, my time is very

I am having trouble understanding the stack allocation scheme when using a C55xx device. From what I can tell, the GLOBAL_STACK_SIZE is set in arch.h to 100,000 bytes (when using FIXED_POINT), which is then used in the ALLOC_STACK macro found in stack_alloc.h. This macro seems to say, if global_stack==0, then call celt_alloc_scratch, found in os_support.h, which in turn attempts to allocate (using

Hi, I am looking into fixed-point code of the CELT decoder for real-time application. Here are some questions.. [1] array, window[] The array, window[] is being initialized from a function below in modes.c. This array is being initialized differently for the decoder, depending on frame size and sampling freq. of the bitstream .. Could you provide us with fixed-point code for initialization of

Dear Sir, Very glad to send E-mali to you , Im Annie. I have encountered some problems on the way of learning opus, so I would like to consult you. I found "global_stack" was not released after malloc, and malloc memory was too large.So what I want to ask you is whether "global_stack" malloc can have less memory, since the value "GLOBAL_STACK_SIZE" can be

hey guys, I am using the tip of Git and attempting to compile for a C55x DSP. I am running into a couple compile errors and have found the source of the issue. The errors: "celt.c", line 957: error: declaration may not appear after executable statement in block as well as "celt.c", line 2303: error: declaration may not appear after executable statement in block Both of

Hi all ! I just learned about the Opus codec and would like to try it out on my NRF52 (Cortex-M4) target.   I've been struggling a bit with the "trival_example.c" setup but repeatedly run into "hard fault" crashes when stepping through the code. Firstly; for a "bare bone" configuration, does the following compiler directives make sense ? UDEFS =

Hi guys, I'm currently working on a CELT implementation for FMOD, and one of the things we want to do is have all memory required allocated beforehand. This is before we have any information about what sounds will be played. We would like to create all of our CELTDecode instances up front. Because celt_mode_create() requires a sample rate and number of channels passed in, this

hi Jean-Marc, the memory after the allocated space is definitely destroyed. It took me some time to find out why. I expected local arrays to be allocated on stack, not on the heap. The function get_required_bits allocates a local array uint32[] which will be located on heap right after the array fromcompute_pulse_cache(), what made me think it was written behind its end. I am sorry for the

Hello, I needed to apply the attached little patch rep_clz to get __adddf3 working on 32Bit x86 Linux. __adddf3 doesn't seem to be part of the Library on any currently supported Platforms. But if support for plattforms without FPU should be added this probably is the correct version. Christoph -------------- next part -------------- A non-text attachment was scrubbed... Name: rep_clz.patch

Hello, I am trying to compile Speex on RealView Compiler and a lot of errors are indicated by compiler: libspeex\bits.c(48): error: #77-D: this declaration has no storage class or type specifier libspeex\bits.c(48): error: #65: expected a ";" libspeex\bits.c(139): warning: #12-D: parsing restarts here after previous syntax error libspeex\bits.c(141): error: #77-D: this declaration

[CCing the libguestfs mailing list - as Rich responded on IRC about your question on timeout.] On Sun, Feb 21, 2016 at 10:07 PM, Thomas Kee <xsited@yahoo.com> wrote: > Hi Kashyap, > > Thanks for offering to help. The day job caused a pause and it took me an > hour to reassert where I was in the process. I usually hang out on freenet > as xsited. I am still reading the

Hi guys, It looks to me like line 955 in celt.c should be: effectiveBytes = vbr_rate>>(3+BITRES); otherwise it seems like "effectiveBytes" is 8 times larger than it should be (at least if it's really meant to be bytes). Cheers, John Ridges

On Nov 7, 2011, at 1:04 AM, Seb wrote: > Hi all, > > I was wondering how I can get a list of ARM NEON intrinsics supported by LLVM. Is there any documentation about them or IntrinsicARM.td file is the only resource I can use ? LLVM implements the standard set of intrinsics defined by ARM. You can find them listed in ARM's documentation. See Appendix E of the RealView® Compilation

Hi all, I was wondering how I can get a list of ARM NEON intrinsics supported by LLVM. Is there any documentation about them or IntrinsicARM.td file is the only resource I can use ? Thanks for your answers Best Regards Seb -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20111107/fade76cc/attachment.html>

Hi all, I'm trying to build the celt package on the Texas TMS320VC5510 DSK. I think there are some #define for it in the code, but I'm doing something wrong. Is there any documentation about it? So far I'm building with the TI_C5X_ASM;CONFIG_TI_C55X #define. Any help? Thank you. Giovanni

I realize this is ancient history, but I am trying to compile Ver 8.1 (from the download page) using Fixed Point and am getting compile errors as follows: argument of type "celt_sig *" is incompatible with parameter of type "celt_int16 *" libcelt81_orig_DSP/libcelt celt.c line 321 1304524612394 19769 argument of type "celt_sig *" is incompatible

Hi, I've recently successful built and run CELT under Windows using "testcelt.c" example file. Since I'm about to port it on a embedded platform i activated the FIXED_POINT #define. I included fixed_generic.h and without other changes to the code i tried to encode and decode the same file i previously used. The output though is completely saturated i.e. it jumps from -32768 to

This should help us to: - More easily add or remove machine initialization arguments without having to change every single machine init function; - More easily make mechanical changes involving the machine init functions in the future; - Let machine initialization forward the init arguments to other functions more easily. This change was half-mechanical process: first the struct was added

Adjust indentation from spaces to tab (+optional two spaces) as in coding style with command like: $ sed -e 's/^ /\t/' -i */Kconfig Signed-off-by: Krzysztof Kozlowski <krzk at kernel.org> --- drivers/acpi/Kconfig | 8 +- drivers/ata/Kconfig | 12 +-- drivers/auxdisplay/Kconfig | 14 +--

Adjust indentation from spaces to tab (+optional two spaces) as in coding style with command like: $ sed -e 's/^ /\t/' -i */Kconfig Signed-off-by: Krzysztof Kozlowski <krzk at kernel.org> --- drivers/acpi/Kconfig | 8 +- drivers/ata/Kconfig | 12 +-- drivers/auxdisplay/Kconfig | 14 +--