Re: [fpc-devel] about freepascal for mips
Fuxin Zhang zhan...@lemote.com wrote: Hello everybody, I am Fuxin Zhang from lemote, now we are working on mips support of fpc 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 ;-) ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] about freepascal for mips
Fuxin Zhang zhan...@lemote.com wrote: Hello everybody, I am Fuxin Zhang from lemote, now we are working on mips support of fpc 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）? You can contact be...@lemote.com to buy. And I've declared that we can donate some for developers. Best Regards ___ 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
Jeppe Gr�sdal Johansen wrote: Does anyone know if there's an easy way to set up an emulator for testing? Been fighting with qemu for the last half hour without results. http://wiki.lazarus.freepascal.org/Qemu_and_other_emulators When I tried to follow the instructions in given link, I met a problem: formatting of the file system took ages. Finally I give up and instead go to my Yeeloong and install a fresh new squeez system. The installed root file system is shared here: http://www.kuaipan.com.cn/file/id_46718218999435672.htm (~150MB) You can download it, generate a virtual disk by yourself and then copy the content to get a working qemu image. Details: 1, use raw disk image format in order to operate it without qemu dd if=/dev/zero of=imgfilename bs=4096 count=xxx(size/4096) 2, losetup /dev/loop0 imgfilename 3, fdisk /dev/loop0, make at least one ext3 partition 4, losetup -d /dev/loop0 5, losetup -o offset_of_the_partition /dev/loop0 imgfilename 6, mkfs.ext3 /dev/loop0 7, mount /dev/loop0 /mnt 8, cp -a (extracted root file system contents) /mnt 9, umount /mnt 10, boot qemu with: qemu-system-mipsel -m 256 -M malta -kernel vmlinux-2.6.32-5-4kc-malta -hda mipsel_hda.img --nographic --append root=/dev/sda1 11, done the root password is 'fpc'. offset_of_the_partition can be calculated with fdisk info: fdisk -l /dev/loop0 Disk /dev/loop0: 17.2 GB, 17179869184 bytes 255 heads, 63 sectors/track, 2088 cylinders, total 33554432 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00066a04 Device Boot Start End Blocks Id System /dev/loop0p120483145921015728581+ 83 Linux /dev/loop0p23145921133554303 1047546+ 82 Linux swap / Solaris offset = start_sector * sector size = 2048 * 512 = 1048576 if you're not confident to do the above, you can download my ready make image from: http://www.lemote.com/upfiles/mipsel-qemu-img.tar.gz (~600MB, kernel/initrd/image/run_mips script) An important point is that in most cases, whoever rolls a distro for a guest system will assume that the user is running directly on the host, i.e. that the guest's console can open in an xterm. At least until you know what's going on, if you do have to access the host system over a network (i.e. rather than having a directly-connected screen and keyboard) start off with a graphical login using e.g. VNC. -- Mark Morgan Lloyd markMLl .AT. telemetry.co .DOT. uk [Opinions above are the author's, not those of his employers or colleagues] ___ 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] Testing Intel/AMD AVX-Implemenation
Hi, Am 03.05.2012 20:25, schrieb Florian Klämpfl: Comments: - I'am not happy with the new fields localvarsize and localconstoffset in rautils.toprrec. Increasing the size of toprrec will probably increase memory usage of the compiler, I also didn't get yet the use of the fields: localsym and localsymofs should allow to figure out the same? Don't understand this. The lifetime of a Tx86Instruction-Instance (and the childs Tx86Operand) on i386 and x86_64 platform is very short. I don't known on other platforms. If is a problem, then i can move the new fields to Tx86Operand. - What's the advantage of the change in itx86int.findreg_by_intname? - You use often begin statement end; While we follow only a few formatting rules in the compiler, I think this is very hard to read. - What does rax86.IntToStr? - I tried to figure out but why is tinsentry.flags a int64? - I made a pascal wrapper around http://sourceware.org/cgi-bin/cvsweb.cgi/src/gas/testsuite/gas/i386/avx.s?rev=1.8content-type=text/x-cvsweb-markupcvsroot=src and get: tavx1.pp(93,9) Error: Unrecognized opcode vcmpeqpd tavx1.pp(93,18) Error: Assembler syntax error tavx1.pp(94,9) Error: Unrecognized opcode vcmpeqpd tavx1.pp(94,19) Error: Assembler syntax error tavx1.pp(95,9) Error: Unrecognized opcode vcmpltpd tavx1.pp(95,18) Error: Assembler syntax error tavx1.pp(96,9) Error: Unrecognized opcode vcmpltpd tavx1.pp(96,19) Error: Assembler syntax error tavx1.pp(97,9) Error: Unrecognized opcode vcmplepd tavx1.pp(97,18) Error: Assembler syntax error tavx1.pp(98,9) Error: Unrecognized opcode vcmplepd tavx1.pp(98,19) Error: Assembler syntax error tavx1.pp(99,9) Error: Unrecognized opcode vcmpunordpd tavx1.pp(99,21) Error: Assembler syntax error tavx1.pp(100,9) Error: Unrecognized opcode vcmpunordpd tavx1.pp(100,22) Error: Assembler syntax error tavx1.pp(101,9) Error: Unrecognized opcode vcmpneqpd tavx1.pp(101,19) Error: Assembler syntax error tavx1.pp(102,9) Error: Unrecognized opcode vcmpneqpd tavx1.pp(102,20) Error: Assembler syntax error tavx1.pp(103,9) Error: Unrecognized opcode vcmpnltpd tavx1.pp(103,19) Error: Assembler syntax error tavx1.pp(104,9) Error: Unrecognized opcode vcmpnltpd tavx1.pp(104,20) Error: Assembler syntax error tavx1.pp(105,9) Error: Unrecognized opcode vcmpnlepd tavx1.pp(105,19) Error: Assembler syntax error tavx1.pp(106,9) Error: Unrecognized opcode vcmpnlepd tavx1.pp(106,20) Error: Assembler syntax error tavx1.pp(107,9) Error: Unrecognized opcode vcmpordpd tavx1.pp(107,19) Error: Assembler syntax error tavx1.pp(108,9) Error: Unrecognized opcode vcmpordpd tavx1.pp(108,20) Error: Assembler syntax error tavx1.pp(109,9) Error: Unrecognized opcode vcmpeq_uqpd tavx1.pp(109,21) Error: Assembler syntax error tavx1.pp(110,9) Error: Unrecognized opcode vcmpeq_uqpd tavx1.pp(110,22) Error: Assembler syntax error tavx1.pp(111,9) Error: Unrecognized opcode vcmpngepd tavx1.pp(111,19) Error: Assembler syntax error tavx1.pp(112,9) Error: Unrecognized opcode vcmpngepd tavx1.pp(112,20) Error: Assembler syntax error tavx1.pp(113,9) Error: Unrecognized opcode vcmpngtpd tavx1.pp(113,19) Error: Assembler syntax error tavx1.pp(114,9) Error: Unrecognized opcode vcmpngtpd tavx1.pp(114,20) Error: Assembler syntax error tavx1.pp(115,9) Error: Unrecognized opcode vcmpfalsepd tavx1.pp(115,21) Error: Assembler syntax error tavx1.pp(116,9) Error: Unrecognized opcode vcmpfalsepd tavx1.pp(116,22) Error: Assembler syntax error tavx1.pp(117,9) Error: Unrecognized opcode vcmpneq_oqpd tavx1.pp(117,22) Error: Assembler syntax error Besides this, the changes look already very good to me! ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel best regards Torsten ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
