> -----Message d'origine----- > De : [email protected] [mailto:fpc-devel- > [email protected]] De la part de Mark Morgan Lloyd > Envoyé : dimanche 29 janvier 2012 15:19 > À : [email protected] > Objet : Re: [fpc-devel] Bounty for MIPS > > Florian Klämpfl wrote: > > Main problem with MIPS is to get hands on a reasonable development > > system (full fledged unix like Debian Linux, *BSD, CPU in the range of 1 > > GHz, 128 MB or more RAM, at least 1 GB of HD/SSD). Cross compiling is > > possible of course, but it makes testing and bug fixing very tedious. If > > ssh to such a system is available, I'll look into fixing the MIPS port > > without any bounty. > > My experience is that Qemu's support of a MIPS target isn't bad, > although what I've done so far has been cross-hosted which was certainly > good enough for compilation of e.g. the compiler in isolation. > > Didn't somebody already have loan hardware for this? > > I'd certainly be happy to continue chugging away at testing once the > assembler reader issue was sorted out- at least until the next > insurmountable problem :-) It seems that David Zhang's compiler already had such a reader, I will try to adapt it if I find the time.
Questions: It seems like GNU AS has a different MUPS syntax as traditional MIPS assembler, but I didn't find precise information about this; Could someone give me some pointers? Pierre PS: I do have access to a GCC Compile farm machine running on gcc42 160G 0.8 GHz ICT Loongson 2F / 512 MB RAM / Lemote Fuloong 6004 Linux mini PC / Debian mipsel muller@gcc42:~$ uname -a Linux gcc42 2.6.27.1 #476 Tue Oct 20 14:25:23 CST 2009 mips64 GNU/Linux No idea how that machine would compare to the one we were talking about here. _______________________________________________ fpc-devel maillist - [email protected] http://lists.freepascal.org/mailman/listinfo/fpc-devel
