This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: FW: Porting gcc to TI TMS320c28x

From: Jim Wilson <wilson at specifixinc dot com>
To: fdalsace <fdalsace at yahoo dot fr>
Cc: gcc at gcc dot gnu dot org
Date: Thu, 08 Jul 2004 12:32:40 -0700
Subject: Re: FW: Porting gcc to TI TMS320c28x
References: <001901c46352$5e42ca00$6701a8c0@NEVO>

fdalsace wrote:

I would like to know about how much time it could need to port gcc for the
TMS320C28x. The assembler if this micro is close to the c30/c40. gcc has
already been ported for the c30/c40.

There are many factors that affect the time needed for a port: the architecture, the ABI, whether source code and/or object file compatibility is required with other tools, etc. There is no easy answer to this question.

A quick rule of thumb is that it will take 3 months to do a port from scratch for a typical RISC target. This assumes you know what you are doing, or have someone you can ask for help. If not, it may take longer. DSP ports are usually harder than RISC ports. You may need binutils and/or newlib ports to get to the point when you can run code. Then you will need a gdb port to debug the running code.

If the c28x really is similar to the c30/c40, then you may be able to just tweak the existing port which could take substantially less time. However, how much time this takes depends on how similar the architecture are. Just because they assembly language code is similar doesn't mean that the architectures are similar. There is no way to give a good estimate with the info you have provided so far. -- Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com

References:
- FW: Porting gcc to TI TMS320c28x
  - From: fdalsace

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]