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: GCC Port (gcc backend) for Microchip PICMicro microcontroller


I am interested by your work, you can share it. What was your Gcc
development version ?

Le mercredi 08 mars 2006 Ã 18:56 +0100, Gabriele Caracausi a Ãcrit :
> Hi Francois, Colm,
> 
> I've read your emails and I'd like to be involved in this project.
> 
> As you can read in my past emails in the GCC ML, I've tried two years ago to create a porting of GCC to PIC 18FXXX.
> 
> The project was developed when I was student without a truly and strong guide in all involved activities.
> My proposal is: I could share the code I've developed but, keep in mind, that the code should contain some error.
> 
> Starting from it, we could continue / modify / correct / improve the porting all together. What do you think about it ? 
> 
> Ciao! 
> Gabriele.
> 
> 
> 
> 
>  
> 
> -----Original Message-----
> From: FranÐois Poulain [mailto:fpoulain@enib.fr] 
> Sent: Monday, March 06, 2006 7:56 PM
> To: Colm O' Flaherty
> Cc: damien.thebault@laposte.net; gcc@gnu.org; tbird-contact@cox.net; gabriele@caracausi.it; dj@redhat.com; mrs@apple.com; Kevin.Tucker@Microchip.com; Lmjennings@ra.rockwell.com; raimund@vmars.tuwien.ac.at; mjv@x64.com; trebor@trebor.org; vrokas@otenet.gr; alex@monaghan.co.uk; dooms@student.info.ucl.ac.be; denisc@overta.ru; aph@redhat.com; matz@suse.de; dave@cyclicode.net; eric.robert@videotron.ca; Svein.Seldal@solidas.com
> Subject: Re: GCC Port (gcc backend) for Microchip PICMicro microcontroller
> 
> > Like you, I'm still studying the internals of gcc, but I'm close to 
> > being confident enough to start making some changes.
> 
> Nice !
> 
> Le lundi 06 mars 2006 Ð 17:17 +0000, Colm O' Flaherty a Ðcrit :
> > Francois,
> > 
> > There are only 35 instructions in the 14 bit instruction set, and 
> > given that, in gcc, the main initial work seems to be in describing 
> > the targets instruction set, it might not take much to find out what 
> > implementation issues will occur, by just taking to the time to describe the instructions.
> > For me, the things that I suspect to be issues are:
> > 
> > -8 bit ALU
> > -small memory space
> > -limited stack space (8 levels on 16F) -the number of PIC devices 
> > (configurations) that would need to be supported (with the various 
> > number of banks, and memory configs)
> > 
> > Like you, I'm still studying the internals of gcc, but I'm close to 
> > being confident enough to start making some changes.
> > 
> > Colm
> 


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