Displaying 4 results from an estimated 4 matches for "dusing".
Did you mean:
using
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)
Anton Korobeynikov schrieb:
> Hello, Philipp.
>
>> unsigned is 16 bit on my target platform.
> Could you please show LLVM bytecode?
>
I've attached the .bc file and the .c source and output files.
I compiled dusing llvm-gcc (not configured as cross-compiler though, so
that might be the problem).
Nevertheless I don't really see why portable source shouldn't be
translated into portable source.
Philipp
-------------- next part --------------
A non-text attachment was scrubbed...
Name: test.bc
Type: app...
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
2009 Jul 23
1
[PATCH server] changes required for fedora rawhide inclusion.
Signed-off-by: Scott Seago <sseago at redhat.com>
---
AUTHORS | 17 ++++++
README | 10 +++
conf/ovirt-agent | 12 ++++
conf/ovirt-db-omatic | 12 ++++
conf/ovirt-host-browser | 12 ++++