Displaying 4 results from an estimated 4 matches for "idefin".
Did you mean:
idefix
2008 Jan 05
0
Assembly on Mac OS needs to be relocatable
I'm trying to port flac 1.2.1 to OS X (I'm taking over maintainership
of the Fink package), and I'm running into some problems with
bitreader_asm.nasm. After adding the following to nasm.h:
+%elifdef OBJ_FORMAT_macho
+ %define FLAC__PUBLIC_NEEDS_UNDERSCORE
+ %idefine code_section section .text
+ %idefine data_section section .data
+ %idefine bss_section section .bss
I can get it compiling, but when it tries to link the libFLAC dylib,
it complains:
ld: warning codegen in
FLAC__bitreader_read_rice_signed_block_asm_ia32_bswap.c1_loop (offset
0x0000003A)...
2008 May 02
0
[LLVMdev] Pointer sizes, GetElementPtr, and offset sizes
...particular pointer size, from
> the compiler. While it does this fine for pointer addresses, it does not
> manage it for address offsets. Consider the following code:
>
> $ cat test.c
> int main() {
> int *x[2];
> int **y = &x[1];
> return (y - x);
> }
Idefine i32 @main() nounwind {
entry:
%x = alloca [2 x i32*] ; <[2 x i32*]*> [#uses=2]
%tmp1 = getelementptr [2 x i32*]* %x, i32 0, i32 1
; <i32**> [#uses=1]
%tmp23 = ptrtoint i32** %tmp1 to i32 ; <i32> [#uses=1]
%x45 = ptrtoint [2 x...
2000 Jun 26
2
Looking for protect()
...xternal symbol _Rf_protect
out.obj : error LNK2001: unresolved external symbol _Rf_allocMatrix
out.obj : error LNK2001: unresolved external symbol _Rf_length
I see, for example, that PROTECT(s) is #defined as protect(s) in R.h,
#ifndef R_NO_REMAP. If I do nothing, I get the errors above, and if I
#idefine R_NO_REMAP, I get the following errors, instead:
Compiling...
out.c
Linking...
out.obj : error LNK2001: unresolved external symbol _unprotect
out.obj : error LNK2001: unresolved external symbol _protect
out.obj : error LNK2001: unresolved external symbol _allocMatrix
out.obj : error LNK2001: unre...
2008 May 02
4
[LLVMdev] Pointer sizes, GetElementPtr, and offset sizes
The LLVA and LLVM papers motivate the GetElementPtr instruction by arguing
that it abstracts implementation details, in particular pointer size, from
the compiler. While it does this fine for pointer addresses, it does not
manage it for address offsets. Consider the following code:
$ cat test.c
int main() {
int *x[2];
int **y = &x[1];
return (y - x);
}
$ llvm-gcc -O3 -c test.c