C54x port: some general technical questions

2005-04-29 Thread Jonathan Bastien-Filiatrault
Hello every one,
   Me and Brian Richter are in the early development stage of the TI
C54x DSP port of GCC. We have some technical/project management questions. I'll
keep it short, so here it is:
* How do we officially become maintainers of this port ? We are presently in the 
process of filling out the copyright assignment forms. We have some code but it 
is far from complete. I was thinking of having a development branch in the main 
CVS tree that would get merged into mainline when ready.

* We have defined BIT_PER_WORD to 16 and UNITS_PER_WORD to 1. On this
DSP, there are two 40-bits accumulators. How do we make GCC take
advantage of this and which machine mode do we use ? I do not think
using HImode for these registers would be the best thing. Would a "custom" mode 
be necessary ? Suggestions welcome.

Thank you for your time,
   Jonathan



GCC Porting advice needed

2005-05-16 Thread Jonathan Bastien-Filiatrault
Hi list,

We are currently making a port for the TMS320C54x, I have some questions
on how to implement certain operations. Most arithmetic operations on
this machine are affected by flags which control how the operations do
sign-extension and overflow. These are called the "SXM" and "OVM" flags
respectively. These flags are stored in two registers along with carry
and other flags. I am somewhat confused as what CCmodes I should have to
use these flags. I also need to know how to test these flags in insns to
be able to do a "if_then_else" in rtl. One other possibility would be to
use "unspec" patterns, but I do not know how well GCC handles these.

Any advice would be appreciated. It would also be great if an
experienced GCC developer could give us a hand in the undertaking of
this project, we are currently running partially blind in some areas.

Happy Hacking,
Jonathan


signature.asc
Description: OpenPGP digital signature


GCC port for the TI TMS320C5{4,5}x

2005-06-13 Thread Jonathan Bastien-Filiatrault
Hello,
We are currently looking for experienced GCC hackers to help
implement and complete a GCC port for the Texas Instruments TMS320C54x.
This chip is used in the Neuros music player, as well as in the Nokia
770 internet tablet. Joe Born of NeurosAudio is ready to compensate
porters for their time. Meanwhile, me and other people who have very
little experience with GCC have put some code together in an effort to
have a fully working port, the project homepage is at
http://gcc-c54x.berlios.de. However, our lack of experience is catching
up with us, there is a lot that we do not understand at this point, we
need somebody who is willing to act as a mentor to this project, at
least long enough to get it off the ground.

Any help/advice is welcome,

Cheers,
Jonathan Bastien-Filiatrault


signature.asc
Description: OpenPGP digital signature


Re: Making a new cross-compile target: where to begin?

2005-10-19 Thread Jonathan Bastien-Filiatrault
[EMAIL PROTECTED] said:
> Hi,
>
> I know that some people are working on a GCC port for Minix v3, but
> I'd like to work on a cross-compiler for my own purposes.  I'd like
> the host and build to be i686-pc-linux-gnu, and the target to be
> i[3456]86-pc-minix3.
>
> Can anyone give me some advice on where to begin and what info I need?
>  The most obvious issue is that binutils needs to be aware of the
> Minix 3 a.out object file format, unless I tweak things so that a
> program that converts statically linked ELF object files into a.out
> object files runs automatically after a build.  I'm not sure what the
> best approach would be.
Well, Daniel Kegel's crosstool is the best place to learn on how to
_build_ a cross compiling toolchain.


> There are probably some good docs out there on making a new
> cross-compile target, but I haven't found them.  Do they exist, and if
> yes where are they?  What new files do I need to help GCC build for a
> Minix 3 target, what do I put in them, where can I learn about writing
> a specs file for Minix 3, etc.
Well, as far as I have seen, most of the internals are documented in the
code itself. The best way to learn how it works, in my opinion, is to get
a good code cross-reference tool. The files you mostly want to look at are
in gcc/config in a build tree.

[snip]
> Thanks for your help.
>
> James Buchanan
>

Good luck and have fun,
Jonathan Bastien-Filiatrault