This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils 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: c4x - TMS320C30-40


"Svein E. Seldal" <Svein.Seldal@solidas.com> writes:

> Ralf Corsepius wrote:
> > IMO, then, binutils (!) should not accept "c4x".
> 
> Well this is easier said than done. When Michael Hayes ported the c4x
> port to the gcc, it was named 'c4x'. All files for this port is
> located in the gcc/config/c4x directory.
> 
> Later it was decided that the official name for this target should be
> 'tic4x', not 'c4x', mainly because there are other Texas Instruments
> (hence ti) targets that has applied this scheme. 'tic4x' is a more
> descriptive name than 'c4x', and coexists better with other targets.
> 
> However, the gcc still uses the 'c4x' name, simply because all the
> files have been checked in under the 'c4x' name. Because you cannot
> simply rename the gcc/config/c4x to gcc/config/tic4x, gcc uses the c4x
> as its native target name. So gcc needs alias 'tic4x' as a 'c4x'
> target.

There's nothing in GCC that prevents the target files for 'tic4x' from
living in 'gcc/config/c4x'.  Look at xstormy16 (in config/stormy16)
and powerpc (in config/rs6000) for examples.

-- 
- Geoffrey Keating <geoffk@geoffk.org>


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