Displaying 10 results from an estimated 10 matches for "transport_triggered_architectures".
Did you mean:
transport_triggered_architecture
2007 Nov 05
6
[LLVMdev] allocating registers less "sparingly"
Hello LLVM people,
Our customizable TTA target [1] is capable of having plenty of registers
and register file ports to improve instruction level parallelism and
reduce spills. It's totally up to the designer of the particular TTA
processor how much the processor has registers and register file resources
along with other TTA components.
We have ported LLVM 2.1 to produce an intermediate TTA
2006 Nov 02
4
[LLVMdev] LLVM and libc
We are going to use LLVM in a compiler project for transport
triggered processors. See Wikipedia for more on transport triggering:
<http://en.wikipedia.org/wiki/Transport_Triggered_Architectures>.
One thing we need is some sort of libc. We are targeting embedded
systems, and I have been looking at things like newlib. Are there
people out there doing something similar? Or any advice or opinions
as to how go about the whole thing?
--
Pertti
2007 Nov 06
0
[LLVMdev] allocating registers less "sparingly"
On Nov 5, 2007, at 2:55 AM, Pekka Jääskeläinen wrote:
> Hello LLVM people,
>
> Our customizable TTA target [1] is capable of having plenty of
> registers
> and register file ports to improve instruction level parallelism and
> reduce spills. It's totally up to the designer of the particular TTA
> processor how much the processor has registers and register file
>
2006 Nov 09
2
[LLVMdev] LLVM and newlib progress
This is in response to Reid's and John's comments about
intrinsics.
The setting of the work is a project on reconfigurable
processors using the Transport Triggered Architecture (TTA)
<http://en.wikipedia.org/wiki/Transport_triggered_architecture>.
For the compiler this means that the target architecture
is not fixed, but rather an instance of a processor template.
Different
2009 Mar 27
0
[LLVMdev] Announcing the Open Source Release of TTA-Based Codesign Environment (TCE) 1.0
TTA-Based Codesign Environment (TCE) is a toolset for designing
application-specific processors (ASP) based on the Transport Triggered
Architecture (TTA). TTA is a minimalistic processor architecture
template that allows high level of control for the designer to choose
the boundary between the hardware and the software.
The toolset provides a complete codesign flow from C programs down to
2009 Mar 27
1
[LLVMdev] Announcing the Open Source Release of TTA-Based Codesign Environment (TCE) 1.0
TTA-Based Codesign Environment (TCE) is a toolset for designing
application-specific processors (ASP) based on the Transport Triggered
Architecture (TTA). TTA is a minimalistic processor architecture
template that allows high level of control for the designer to choose
the boundary between the hardware and the software.
The toolset provides a complete codesign flow from C programs down to
2007 Nov 05
0
[LLVMdev] allocating registers less "sparingly"
On Nov 5, 2007, at 2:55 AM, Pekka Jääskeläinen wrote:
> Hello LLVM people,
>
> Our customizable TTA target [1] is capable of having plenty of
> registers
> and register file ports to improve instruction level parallelism and
> reduce spills. It's totally up to the designer of the particular TTA
> processor how much the processor has registers and register file
>
2006 Nov 09
0
[LLVMdev] LLVM and newlib progress
Pertti Kellomäki wrote:
> This is in response to Reid's and John's comments about
> intrinsics.
>
> The setting of the work is a project on reconfigurable
> processors using the Transport Triggered Architecture (TTA)
> <http://en.wikipedia.org/wiki/Transport_triggered_architecture>.
> For the compiler this means that the target architecture
> is not fixed, but
2006 Nov 09
0
[LLVMdev] LLVM and newlib progress
Hi Pertti,
On Thu, 2006-11-09 at 15:29 +0200, Pertti Kellomäki wrote:
> I managed to compile newlib with llvm-gcc yesterday. That
> is, the machine independent part is now basically done, and
> the syscall part contains no-op stubs provided by libgloss.
> I haven't tested the port yet, but since newlib has already
> been ported to many architectures, I would be pretty surprised
2006 Nov 09
9
[LLVMdev] LLVM and newlib progress
I managed to compile newlib with llvm-gcc yesterday. That
is, the machine independent part is now basically done, and
the syscall part contains no-op stubs provided by libgloss.
I haven't tested the port yet, but since newlib has already
been ported to many architectures, I would be pretty surprised
if there were any major problems.
A couple of things I noticed when configuring newlib for