Re: [O-MPI users] MIPS64 - The Long-Awaited Config File
I'll try the MIPS (aka MIPS32) solution - hey, it can't kill anything. There are some subtle differences, but most MIPS64 boards'll run MIPS32 code (I think in a similar way to the way AMD's 64-bit chips also run 32-bit code). However, for anyone planning a "native" MIPS64 solution, I've found a few technical documents that seem to cover the material wanted: The basic MIPS64 (and MIPS32) specification, instruction set, et al, can be found at: http://www.mips.com/content/Documentation/MIPSDocumentation/ProcessorCores/doclibrary Free registration is required to download the manuals. The Broadcom manual specifically for the SB1 chip and the boards Broadcom uses them in can be found at: http://sibyte.broadcom.com/public/resources/ Although I can't see this being overly useful for OpenMPI, the SB1 also implements HyperTransport. http://www.hypertransport.org/tech/tech_specs.cfm It might be useful if someone was writing some really exotic stuff, though, and I've found it's almost impossible to have too many manuals. __ Yahoo! for Good Watch the Hurricane Katrina Shelter From The Storm concert http://advision.webevents.yahoo.com/shelter
[O-MPI users] MIPS64 Trek - The story so far
Hi, Just a quick update on working with OpenMPI's MIPS code on the MIPS64 processor. It does not appear to work to simply use the atomic code for the 32-bit MIPS - the opcodes don't correspond. Over the next day or two, I will be updating the assembler on the MIPS64 board, and I'll know better then whether this is a genuine problem or a phantom issue. (If someone's developed a patch by then, so much the better, but I'm going to keep working on this possibility for the immediate future.) atomic-asm.s: Assembler messages: atomic-asm.s:8: Error: unrecognized opcode `leaf(opal_atomic_mb)' atomic-asm.s:13: Error: unrecognized opcode `end(opal_atomic_mb)' atomic-asm.s:17: Error: unrecognized opcode `leaf(opal_atomic_rmb)' atomic-asm.s:22: Error: unrecognized opcode `end(opal_atomic_rmb)' atomic-asm.s:25: Error: unrecognized opcode `leaf(opal_atomic_wmb)' atomic-asm.s:30: Error: unrecognized opcode `end(opal_atomic_wmb)' atomic-asm.s:33: Error: unrecognized opcode `leaf(opal_atomic_cmpset_32)' atomic-asm.s:49: Error: unrecognized opcode `end(opal_atomic_cmpset_32)' atomic-asm.s:52: Error: unrecognized opcode `leaf(opal_atomic_cmpset_acq_32)' atomic-asm.s:69: Error: unrecognized opcode `end(opal_atomic_cmpset_acq_32)' atomic-asm.s:72: Error: unrecognized opcode `leaf(opal_atomic_cmpset_rel_32)' atomic-asm.s:89: Error: unrecognized opcode `end(opal_atomic_cmpset_rel_32)' atomic-asm.s:92: Error: unrecognized opcode `leaf(opal_atomic_cmpset_64)' atomic-asm.s:108: Error: unrecognized opcode `end(opal_atomic_cmpset_64)' atomic-asm.s:111: Error: unrecognized opcode `leaf(opal_atomic_cmpset_acq_64)' atomic-asm.s:127: Error: unrecognized opcode `end(opal_atomic_cmpset_acq_64)' atomic-asm.s:130: Error: unrecognized opcode `leaf(opal_atomic_cmpset_rel_64)' atomic-asm.s:147: Error: unrecognized opcode `end(opal_atomic_cmpset_rel_64)' make[2]: Leaving directory `/tools/openmpi-1.0a1r7305/opal/asm' __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: [O-MPI users] MIPS64 Trek - The story so far
Gah - shame on me. I let some IRIX-specific stuff slip through. Lemme see if I can find an IRIX box and clean that up. The problems you listed below are not MIPS 32 / MIPS 64 issues, but the use of some nice IRIX-specific macros. By the way, to clarify, the assembly has been tested on a MIPS R14K in 64 bit mode (and 32 bit mode using SGI's n32 ABI -- it will not work with their o32 ABI). Just not on anything other than IRIX ;). Brian On Sep 12, 2005, at 6:13 PM, Jonathan Day wrote: Hi, Just a quick update on working with OpenMPI's MIPS code on the MIPS64 processor. It does not appear to work to simply use the atomic code for the 32-bit MIPS - the opcodes don't correspond. Over the next day or two, I will be updating the assembler on the MIPS64 board, and I'll know better then whether this is a genuine problem or a phantom issue. (If someone's developed a patch by then, so much the better, but I'm going to keep working on this possibility for the immediate future.) atomic-asm.s: Assembler messages: atomic-asm.s:8: Error: unrecognized opcode `leaf(opal_atomic_mb)' atomic-asm.s:13: Error: unrecognized opcode `end(opal_atomic_mb)' atomic-asm.s:17: Error: unrecognized opcode `leaf(opal_atomic_rmb)' atomic-asm.s:22: Error: unrecognized opcode `end(opal_atomic_rmb)' atomic-asm.s:25: Error: unrecognized opcode `leaf(opal_atomic_wmb)' atomic-asm.s:30: Error: unrecognized opcode `end(opal_atomic_wmb)' atomic-asm.s:33: Error: unrecognized opcode `leaf(opal_atomic_cmpset_32)' atomic-asm.s:49: Error: unrecognized opcode `end(opal_atomic_cmpset_32)' atomic-asm.s:52: Error: unrecognized opcode `leaf(opal_atomic_cmpset_acq_32)' atomic-asm.s:69: Error: unrecognized opcode `end(opal_atomic_cmpset_acq_32)' atomic-asm.s:72: Error: unrecognized opcode `leaf(opal_atomic_cmpset_rel_32)' atomic-asm.s:89: Error: unrecognized opcode `end(opal_atomic_cmpset_rel_32)' atomic-asm.s:92: Error: unrecognized opcode `leaf(opal_atomic_cmpset_64)' atomic-asm.s:108: Error: unrecognized opcode `end(opal_atomic_cmpset_64)' atomic-asm.s:111: Error: unrecognized opcode `leaf(opal_atomic_cmpset_acq_64)' atomic-asm.s:127: Error: unrecognized opcode `end(opal_atomic_cmpset_acq_64)' atomic-asm.s:130: Error: unrecognized opcode `leaf(opal_atomic_cmpset_rel_64)' atomic-asm.s:147: Error: unrecognized opcode `end(opal_atomic_cmpset_rel_64)' make[2]: Leaving directory `/tools/openmpi-1.0a1r7305/opal/asm' __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ users mailing list us...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/users
Re: [O-MPI users] MIPS64 Trek - The story so far
On Mon, Sep 12, 2005 at 07:24:43PM -0500, Brian Barrett wrote: > By the way, to clarify, the assembly > has been tested on a MIPS R14K in 64 bit mode (and 32 bit mode using > SGI's n32 ABI -- it will not work with their o32 ABI). In Linux/binutils lingo, that means it's MIPS64 code, and not MIPS. -- greg
