Displaying 6 results from an estimated 6 matches for "tms320c64x".
Did you mean:
tms320c64+
2011 Oct 27
2
[LLVMdev] Trunc Load
> Hi Johannes, what processor are you targeting? Is it little-endian or
> big-endian?
Little-endian. (The truth: you can set it manually, but it is set to
little endian, for sure.) The processor is a TI TMS320C64x.
Follow-up: I discovered that the "guilty" method is
DAGCombiner::ReduceLoadWidth. The error is introduced because the offset
is not calculated correctly.
The first problem is that the pointer I get for loading does not point
to the address of the low word, but to the address of the...
2011 Oct 27
0
[LLVMdev] Trunc Load
Hi Johannes, what processor are you targeting? Is it little-endian or
big-endian?
Ciao, Duncan.
> I have the following simple IR:
>
> ==================================
> @l = common global i64 0, align 8
>
> define void @hello() nounwind {
> entry:
> store i64 -4919131755279862989, i64* @l
> ret void
> }
>
> define i32 @main(i32 %argc, i8** %argv)
2011 Oct 27
0
[LLVMdev] Trunc Load
...Johannes Birgmeier
<e0902998 at student.tuwien.ac.at> wrote:
>
>> Hi Johannes, what processor are you targeting? Is it little-endian or
>> big-endian?
> Little-endian. (The truth: you can set it manually, but it is set to
> little endian, for sure.) The processor is a TI TMS320C64x.
>
> Follow-up: I discovered that the "guilty" method is
> DAGCombiner::ReduceLoadWidth. The error is introduced because the offset
> is not calculated correctly.
>
> The first problem is that the pointer I get for loading does not point
> to the address of the low wo...
2011 Oct 27
2
[LLVMdev] Trunc Load
Hello!
I have the following simple IR:
==================================
@l = common global i64 0, align 8
define void @hello() nounwind {
entry:
store i64 -4919131755279862989, i64* @l
ret void
}
define i32 @main(i32 %argc, i8** %argv) nounwind {
entry:
call void @hello()
%tmp = load i64* @l
%conv = trunc i64 %tmp to i32
ret i32 %conv
}
==================================
2006 Jan 17
1
What the heck? A Vorbis scam?
...39;s implementation of Ogg Vorbis I Decoder. VOV is an
independent implementation of Ogg Vorbis I Decoder developed from
scratch keeping in mind Memory and MCPS constraints of embedded devices
What are the platforms in which VOV is available?
Currently we have optimized implementation of VOV on TMS320C64x,
TMS320C67x, TMS320C62x family DSPs. We are currently working on porting
and optimization of VOV onto other DSP Platforms. For more information
on the same mail us to info@vinjey.com
What is the Memory requirement for the VOV Decoder?
We have provided MCPS and Memory requirements of VOV decode...
2013 May 13
0
DSPs which are suitable for porting OPUS
Dear Christian van Bijleveld,
You can use any of the below DSPs of Texas Instruments
1. TMS320C674x - This supports floating point implementation of opus
2. TMS320C66x - This supports both floating and fixed point implementations
3. TMS320C64x - This supports only fixed point implementation
Regards,
Mahantesh
On Mon, May 13, 2013 at 10:12 PM, <opus-request at xiph.org> wrote:
> Send opus mailing list submissions to
> opus at xiph.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>...