search for: abi64

On May 24, 2008, at 11:43 AM, Marcel Moolenaar wrote: > All, > > So far I've tried LLVM on amd64, i386, ia64 and powerpc under FreeBSD > and aside for ia64, things look pretty good for a first try. There > are 2 unexpected failures for PowerPC, which appear to be caused by > uninitialized memory. I'm still working on a fix for that (need to > brush up on my C++

All, So far I've tried LLVM on amd64, i386, ia64 and powerpc under FreeBSD and aside for ia64, things look pretty good for a first try. There are 2 unexpected failures for PowerPC, which appear to be caused by uninitialized memory. I'm still working on a fix for that (need to brush up on my C++ skills). [sidenote: In FreeBSD -current, the memory allocator initializes memory with 0xa5

.../dumpster/home/marcel/LLVM/src/llvm/test/CodeGen/Generic/ 2003-05-27-phifcmpd.ll Failed with signal(SIGABRT) at line 1 while running: llvm-as < /dumpster/home/marcel/LLVM/src/llvm/test/ CodeGen/Generic/2003-05-27-phifcmpd.ll | llc .ident "LLVM-ia64" .psr lsb .radix C .psr abi64 Cannot yet select: 0x2000000001d76120: i1 = setcc 0x2000000001d46520, 0x2000000001d48240, 0x2000000001d08fe0 FAIL: /dumpster/home/marcel/LLVM/src/llvm/test/CodeGen/Generic/ 2003-05-27-useboolinotherbb.ll Failed with signal(SIGABRT) at line 1 while running: llvm-as < /dumpster/home/marcel/LLV...

...velopers, GCC[1] is able to use Loongson ISA[2] for instruction selection: $ cat hello.c #include <stdio.h> int main(int argc, char *argv[]) { printf("Hello World\n"); return 0; } $ gcc -O0 -S hello.c $ cat hello.s .file 1 "hello.c" .section .mdebug.abi64 .previous .nan legacy .gnu_attribute 4, 1 .abicalls .rdata .align 3 .LC0: .ascii "Hello World\000" .text .align 2 .globl main .set nomips16 .set nomicromips .ent main .type main, @function mai...

...hain result: 0x1204e00: i64 = LD8 0x1204da0 This patch should help: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20080526/062966.html This now looks like the fp compare issue below. > > > .ident "LLVM-ia64" > > .psr lsb > .radix C > .psr abi64 > Cannot yet select: 0x2000000001d76120: i1 = setcc 0x2000000001d46520, > 0x2000000001d48240, 0x2000000001d08fe0 > > FAIL: /dumpster/home/marcel/LLVM/src/llvm/test/CodeGen/Generic/ > 2003-05-27-useboolinotherbb.ll This looks like ia64 backend isn't handling 'setune' (set...

...lude <stdio.h> >> >> int main(int argc, char *argv[]) { >> printf("Hello World\n"); >> return 0; >> } >> >> $ gcc -O0 -S hello.c >> >> $ cat hello.s >> .file 1 "hello.c" >> .section .mdebug.abi64 >> .previous >> .nan legacy >> .gnu_attribute 4, 1 >> .abicalls >> .rdata >> .align 3 >> .LC0: >> .ascii "Hello World\000" >> .text >> .align 2 >> .globl main >>...

...I's in the form of the Triple::GNUEABI, Triple::GNUEABIHF, and Triple::GNUX32 values of the environment component of the triple and it's up to the frontend and/or API-user to pass the right thing to the backend. For MIPS, I'm defining Triple::GNUABI32, Triple::GNUABIN32, and Triple::GNUABI64. All three of these are supported by tools like binutils (by virtue of a wildcard match '*linux-gnu*') and of these three, Triple::GNUABI32 is not in general use, Triple::GNUABIN32 will be used by Debian if/when we do an N32 port, and Triple::GNUABI64 is currently used by Debian for our N64...

...-time options based on previous discussions. Has this changed? > ps. It also doesn't appear that Matthew (who took over my gcc responsibilities, thanks!) has added support for this in gcc yet either. > echristo at dzur ~/b/build-gcc-mips64abin64> .../configure --target=mips64-linux-gnuabi64 --enable-languages=c > echristo at dzur ~/tmp> ~/builds/build-gcc-mips64abin64/gcc/cc1 foo.c -o - > .file 1 "foo.c" > .section .mdebug.abiN32 It's true that upstream GCC doesn't know about this triple yet but that's because downstream users...