search for: target_ptr_size

Displaying 7 results from an estimated 7 matches for "target_ptr_size".

2010 Aug 09
3
[LLVMdev] llvm "iword" type
.... %classPointer1 = ptrtoint i8** %classPointer to i32 %classPointer2 = and i32 -4, %classPointer1 %realClassPointer = inttoptr i32 %classPointer2 to i8** ... Ideally, I'd like to generate completely architecture-independent code, which brings me to my question: Does LLVM have some sort of i<target_ptr_size> type that I can cast to to do this masking (like size_t in C), instead of generating different LLVM IR for 32- and 64- bit architectures? Thanks, Joshua -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/201...
2010 Aug 09
0
[LLVMdev] llvm "iword" type
...classPointer to i32 > %classPointer2 = and i32 -4, %classPointer1 > %realClassPointer = inttoptr i32 %classPointer2 to i8** > ... > > Ideally, I'd like to generate completely architecture-independent code, > which brings me to my question: Does LLVM have some sort of > i<target_ptr_size> type that I can cast to to do this masking (like size_t > in C), instead of generating different LLVM IR for 32- and 64- bit > architectures? > > Thanks, > > Joshua > > > > _______________________________________________ > LLVM Developers mailing list > LLVMd...
2010 Aug 09
3
[LLVMdev] llvm "iword" type
...%classPointer2 = and i32 -4, %classPointer1 >> %realClassPointer = inttoptr i32 %classPointer2 to i8** >> ... >> >> Ideally, I'd like to generate completely architecture-independent code, >> which brings me to my question: Does LLVM have some sort of >> i<target_ptr_size> type that I can cast to to do this masking (like size_t >> in C), instead of generating different LLVM IR for 32- and 64- bit >> architectures? >> >> Thanks, >> >> Joshua >> >> >> >> _______________________________________________ >...
2010 Aug 09
0
[LLVMdev] llvm "iword" type
...%classPointer1 > >> %realClassPointer = inttoptr i32 %classPointer2 to i8** > >> ... > >> > >> Ideally, I'd like to generate completely architecture-independent code, > >> which brings me to my question: Does LLVM have some sort of > >> i<target_ptr_size> type that I can cast to to do this masking (like > size_t > >> in C), instead of generating different LLVM IR for 32- and 64- bit > >> architectures? > >> > >> Thanks, > >> > >> Joshua > >> > >> > >> > >&g...
2006 Jun 26
0
[klibc 35/43] sparc support for klibc
...dd %l0, %o0, %l0 + addcc %l3, %l1, %i1 + addx %l2, %l0, %i0 + jmp %i7+8 + restore + .size __muldi3, .-__muldi3 diff --git a/usr/klibc/arch/sparc/crt0.S b/usr/klibc/arch/sparc/crt0.S new file mode 100644 index 0000000..63db188 --- /dev/null +++ b/usr/klibc/arch/sparc/crt0.S @@ -0,0 +1,2 @@ +#define TARGET_PTR_SIZE 32 +#include "crt0i.S" diff --git a/usr/klibc/arch/sparc/crt0i.S b/usr/klibc/arch/sparc/crt0i.S new file mode 100644 index 0000000..0220b01 --- /dev/null +++ b/usr/klibc/arch/sparc/crt0i.S @@ -0,0 +1,100 @@ +! This file derived from the equivalent in newlib +! +! C run time start off + +!...
2006 Jun 26
0
[klibc 36/43] sparc64 support for klibc
...arch/$(KLIBCARCH)/setjmp.o \ + arch/$(KLIBCARCH)/syscall.o \ + arch/$(KLIBCARCH)/sysfork.o + +archclean: diff --git a/usr/klibc/arch/sparc64/crt0.S b/usr/klibc/arch/sparc64/crt0.S new file mode 100644 index 0000000..5faee7c --- /dev/null +++ b/usr/klibc/arch/sparc64/crt0.S @@ -0,0 +1,2 @@ +#define TARGET_PTR_SIZE 64 +#include "../sparc/crt0i.S" diff --git a/usr/klibc/arch/sparc64/pipe.S b/usr/klibc/arch/sparc64/pipe.S new file mode 100644 index 0000000..c63b20f --- /dev/null +++ b/usr/klibc/arch/sparc64/pipe.S @@ -0,0 +1,30 @@ +/* + * arch/sparc64/pipe.S + * + * The pipe system call are special on...
2006 Jun 28
35
[klibc 00/31] klibc as a historyless patchset (updated and reorganized)
I have updated the klibc patchset based on feedback received. In particular, the patchset has been reorganized so as not to break git-bisect. Additionally, this updates the patch base to 2.6.17-git12 (d38b69689c349f35502b92e20dafb30c62d49d63) and klibc 1.4.8; the main difference on the klibc side is removal of obsolete code. This is also available as a git tree at: