Re: [fpc-devel] about freepascal for mips
On Sat, 26 May 2012 21:00:23 +0800 (CST) zhan...@lemote.com wrote: microcode wrote Hello and may I say EXCELLENT! Now all we need to know is where to get a good price on your MIPS boxes so we can all run them ;-) Well, we decide to sell some machines at very low price to help promote the mips world. How about Yeeloong netbooks with $100-$150(for various configurations and amounts + shipment? Hi, I was more interested in the single box version. I forget what you call it. I will email Betty, thanks for the connection. I'm looking for a MIPS box for my own study. You can contact be...@lemote.com to buy. And I've declared that we can donate some for developers. If I could help I would be glad to, but unfortunately I am not an fpc developer. So I can't ask for a donation. I can ask for a good price though ;-) Thanks and good luck with fpc. Seems like a great group of guys to me. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] about freepascal for mips
On 25 May 2012, at 15:48, Fuxin Zhang wrote: Now at least we have a very good start. I've a quick look over current mips code, it seems not strong enough. For example, the inverse_cond seems wrong, the setting of first_int_imreg/mavarregs/maxfpuvarregs etc. is hard to understand... first_int_imreg looks correct. It has to be set to the number of integer registers, and since MIPS presumably has 32 integer registers, $20 (= 32 in hex) is ok. maxvarregs/maxfpuvarregs is from the old register variables code and is no longer used. That code still has to be largely removed, and possibly partially updated and reintegrated in the current compiler. Directly starting with compiling a native compiler binary and debugging it, is however probably not the easiest approach. It's better to start with cross-compiling tests and debugging those if they fail. To execute all tests, after you've done the make cycle CPU_TARGET=mipsel, go into fpc/tests, and execute a command like this (make sure to first create the TEST_REMOTEPATH directory on the remote system): make TEST_FPC=/full/path/to/ppcrossmipsel TEST_SSH=login@mips-box TEST_REMOTEPATH=/tmp/tests OPT=-O2 -ap TEST_OPT=-O2 -ap QUICKTEST=1 clean all digest Add any additional parameters you need for cross-compilation (-FD, -XR, ...) to TEST_OPT. The QUICKTEST=1 means that tests that depend on units under fpc/packages won't be checked (there's not that many of them anyway). At the end, the list of failing tests will be in output/mipself-linux/faillist, and in the longlog file in that same directory you'll find the complete compilation/execution logs of the failed tests. When starting to fix things, it's best to first focus on tests from test/cg and test/units/system (apart from the tres* tests, which are for Windows-style resource support), and then everything else under test. Jonas___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] about freepascal for mips
On 27 May 2012, at 21:34, Jonas Maebe wrote: make TEST_FPC=/full/path/to/ppcrossmipsel TEST_SSH=login@mips-box TEST_REMOTEPATH=/tmp/tests OPT=-O2 -ap TEST_OPT=-O2 -ap QUICKTEST=1 clean all digest Add any additional parameters you need for cross-compilation (-FD, -XR, ...) to TEST_OPT. The QUICKTEST=1 means that tests that depend on units under fpc/packages won't be checked (there's not that many of them anyway). Sorry, you need one more parameter due to a bug in the current building infrastructure when dealing with cross-compiled testsuite runs: make FPMAKEFPC=/full/path/to/native-compiler-built-from-same-source-tree-as-cross-compiler TEST_FPC=/full/path/to/ppcrossmipsel TEST_SSH=login@mips-box TEST_REMOTEPATH=/tmp/tests OPT=-O2 -ap TEST_OPT=-O2 -ap QUICKTEST=1 clean all digest Jonas___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] about freepascal for mips
Hi, I was more interested in the single box version. I forget what you call it. I will email Betty, thanks for the connection. I'm looking for a MIPS box for my own study. It is called Fuloong, and I find I made a mistake, betty's mail is zha...@lemote.com, not be...@lemote.com. You can contact be...@lemote.com to buy. And I've declared that we can donate some for developers. If I could help I would be glad to, but unfortunately I am not an fpc developer. So I can't ask for a donation. I can ask for a good price though ;-) Thanks and good luck with fpc. Seems like a great group of guys to me. Thanks, people here are really nice. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] about freepascal for mips
Thank you. -Original Message- From: Fuxin Zhang zhan...@lemote.com Sender: fpc-devel-boun...@lists.freepascal.org Date: Mon, 28 May 2012 07:49:43 To: FPC developers' listfpc-devel@lists.freepascal.org Reply-To: zhan...@lemote.com, FPC developers' list fpc-devel@lists.freepascal.org Subject: Re: [fpc-devel] about freepascal for mips Hi, I was more interested in the single box version. I forget what you call it. I will email Betty, thanks for the connection. I'm looking for a MIPS box for my own study. It is called Fuloong, and I find I made a mistake, betty's mail is zha...@lemote.com, not be...@lemote.com. You can contact be...@lemote.com to buy. And I've declared that we can donate some for developers. If I could help I would be glad to, but unfortunately I am not an fpc developer. So I can't ask for a donation. I can ask for a good price though ;-) Thanks and good luck with fpc. Seems like a great group of guys to me. Thanks, people here are really nice. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
