Displaying 3 results from an estimated 3 matches for "f96d954c".
2006 Nov 24
0
[LLVMdev] Byte code portability (was Re: libstdc++ as bytecode, and compiling C++ to C)
Hello, Philipp.
> unsigned is 16 bit on my target platform.
Could you please show LLVM bytecode?
--
With best regards, Anton Korobeynikov.
Faculty of Mathematics & Mechanics, Saint Petersburg State University.
2006 Nov 24
1
[LLVMdev] Byte code portability (was Re: libstdc++ as bytecode, and compiling C++ to C)
...ble source shouldn't be
translated into portable source.
Philipp
-------------- next part --------------
A non-text attachment was scrubbed...
Name: test.bc
Type: application/octet-stream
Size: 127 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20061124/f96d954c/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: test.c
Type: text/x-csrc
Size: 69 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20061124/f96d954c/attachment.c>
-------------- next part --------------...
2006 Nov 24
4
[LLVMdev] Byte code portability (was Re: libstdc++ as bytecode, and compiling C++ to C)
Reid Spencer schrieb:
> Note that C and LLVM types are *not* the same things (despite the
> similar names). We are in the process of making this abundantly clear.
> The LLVM IR will soon use names like i8, i16, i32, and i64 (signless
> integer quantities of specific sizes, regardless of platform).
I had explicitly specified the size in the input code using a uint32_t
type, the