[fpc-devel] Is target mips-embedded possible / planned?

Florian Klämpfl florian at freepascal.org
Mon May 13 20:36:42 CEST 2013

Am 13.05.2013 20:07, schrieb Michael Ring:
> OK, I got kind of bored last weekend and started to implement
> mips-embedded target. The crosscompiler builds fine and already shows
> the list of (not yet implemented) pic32mx controllers, I am now
> searching through the code for places that I need to change.
> One thing that makes me wonder is how mips and mipsel defines are
> related and when to use the 'mips' and when to use 'mipsel'.

mips: mipsel and mipseb

> Should I use 'mips' wherever posible or are those two really different
> architectures? (Well, OK, one is big and one is little endian, quite a
> difference)
> There's one big favour I would like to ask, Florian, could you please
> enable mipsel-embedded in fpcmake and then re-generate the makefiles?

Yes, I can do so.

> I have done this in my local copy but now a svn diff looks like a big
> mess because all those makefile changes make it hard for me to spot my
> code changes.

Look at svn st -q to identify the changed files.

> I have also had a look at the changeset for avr-embedded, there were a
> lot of changes in the codegen and other places, do you expect that the
> same will need to be done for mips 


> or was avr a special case?

You must always distinguish between port to a new OS (like linux,
"embedded", *BSD, ...) and port a to a new CPU (avr, arm, mips, ...).

BTW: Any news on Cortex-M0?

More information about the fpc-devel mailing list