similar to: [LLVMdev] TTA-Based Codesign Environment (TCE) v1.3 released

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

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

Announcing the Release of TTA-Based Codesign Environment (TCE) v1.2 TTA-Based Codesign Environment (TCE) is a toolset for designing application-specific processors (ASP) based on the Transport Triggered Architecture (TTA). The toolset provides a complete codesign flow from C programs down to synthesizable VHDL and parallel program binaries. Processor customization points include the register

TTA-based Co-design Environment (TCE) is a toolset for design and programming of low power customized processors based on the Transport Triggered Architecture (TTA). The toolset provides a complete retargetable co-design flow from high-level language programs down to synthesizable processor RTL (VHDL and Verilog generation supported) and parallel program binaries. Processor customization points

TTA-based Co-design Environment (TCE) is a toolset for design and programming of low power customized processors based on the Transport Triggered Architecture (TTA). The toolset provides a complete retargetable co-design flow from high-level language programs down to synthesizable processor RTL (VHDL and Verilog generation supported) and parallel program binaries. Processor customization points

TTA-based Co-design Environment (TCE) is a toolset for designing application-specific processors based on the Transport Triggered Architecture (TTA). The toolset provides a complete retargetable co-design flow from high-level language programs down to synthesizable VHDL and parallel program binaries. Processor customization points include the register files, function units, supported operations,

TTA-Based Co-design Environment (TCE) is a toolset for designing application-specific processors (ASP) based on the Transport Triggered Architecture (TTA). The toolset provides a complete retargetable co-design flow from C programs down to synthesizable VHDL and parallel program binaries. Processor customization points include the register files, function units, supported operations, and the

v1.2.rc1 + config rewrite + multi-dbox: http://hg.dovecot.org/dovecot-1.3/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20090403/aa9c0107/attachment-0002.bin>

2010/6/29 Pekka Jääskeläinen <pekka.jaaskelainen at tut.fi>: > Hi, > > I wrote an LLVM blog post about our use of LLVM in the TCE project and a bit > of a background for the TCE project in general. I hope some of you will find > it interesting :) > > http://blog.llvm.org/2010/06/tce-project-co-design-of-application.html I'll ask here (rather than the TCE list)

TTA-based Co-design Environment (TCE) v1.6 released --------------------------------------------------- TTA-based Co-design Environment (TCE) is a toolset for designing application-specific processors based on the Transport Triggered Architecture (TTA). The toolset provides a complete retargetable co-design flow from high-level language programs down to synthesizable processor RTL (VHDL and

Hi, I wrote an LLVM blog post about our use of LLVM in the TCE project and a bit of a background for the TCE project in general. I hope some of you will find it interesting :) http://blog.llvm.org/2010/06/tce-project-co-design-of-application.html -- Pekka

Tar http://www.mediacastone.com/~cvscaster/dev/icecast2_status/v1.3/icecast2_status_v1.3.tar source http://www.mediacastone.com/~cvscaster/dev/icecast2_status/v1.3/source/ Please let me know if there are any bugs or problems admin@mediacast1.com, this script parses the stats.xml file and creates php variables, you will need to create a seperate php page and incorperate your own display results,

Tar http://www.mediacastone.com/~cvscaster/dev/icecast2_status/v1.3/icecast2_status_v1.3.tar source http://www.mediacastone.com/~cvscaster/dev/icecast2_status/v1.3/source/ Please let me know if there are any bugs or problems admin@mediacast1.com, this script parses the stats.xml file and creates php variables, you will need to create a seperate php page and incorperate your own display results,

Advanced Diary (a simple calendar/journaling program)installed fine, but when I go to run it the splash screen for the program shows up then I get an error box that says: Error Creating Object. Please verify that Microsoft Data Access Components 2.1 or later have been properly installed. The program stops there. A google search turned up this a download page for MDAC 2.8 here:

It's getting more and more annoying to have separate plugin directories for lda, pop3 and imap. Currently all the plugins are installed into $lib/dovecot/ and then symlinked to the lda, pop3, imap directories. The original reason was that v0.99 just loaded everything in those directories since there was no mail_plugins setting. But then there are things like expire-tool and convert-tool (and

This makes it possible to wait for a specific amount of time, rather than wait until infinity. Signed-off-by: Maarten Lankhorst <maarten.lankhorst at canonical.com> --- Splitted out version, I've noticed that I forgot to convert radeon_fence_wait_empty to long r, fixed. drivers/gpu/drm/radeon/radeon_fence.c | 60 +++++++++++++++++++++++------------ 1 file changed, 40 insertions(+),

Still broken, but I committed the current changes to http://hg.dovecot.org/dovecot-config-rewrite/ The idea is something like: - src/config/ contains a doveconf binary which can be used to dump the current configuration. It's the only binary that reads dovecot.conf directly. Currently the code is kind of ugly because I wanted it to be able to parse the existing v1.2 dovecot.conf which

Am 02.06.2014 15:14, schrieb Maarten Lankhorst: > This makes it possible to wait for a specific amount of time, > rather than wait until infinity. > > Signed-off-by: Maarten Lankhorst <maarten.lankhorst at canonical.com> > --- > Splitted out version, I've noticed that I forgot to convert > radeon_fence_wait_empty to long r, fixed. >

I was hoping to finally get shared libdovecot.so and libdovecot-storage.so libraries for v1.3, so Sieve (and maybe others) could link against them. But I'm running into trouble getting it to compile in Solaris 10. Could you non-Linux users test if this compiles with you? http://dovecot.org/tmp/dovecot-1.3.UNSTABLE.tar.gz Or if anyone has ideas why this happens, I'd like to know: