Displaying 3 results from an estimated 3 matches for "int32_l".
Did you mean:
int32_t
2008 Sep 29
3
[LLVMdev] Architecture Dependency of LLVM bitcode (was Re: compile linux kernel)
...t; potentially write code that detected endiannes at runtime and chose
> multiversioned code based on that, but that is ugly and optimization
> prohibiting).
>
Why not add types with explicit endianess? A trick I use for reading binary
files across platforms is to define the types int32, int32_le and int32_be :
int32 is platform-native, _le and _be are little and big endian,
respectively. I use and #ifdef in my types.hpp to determine which of _le and
_be is a typedef for the standard uint32, and the other is implemented as a
class with operator int32(). "add i32_be %X, 8" looks e...
2008 Sep 29
0
[LLVMdev] Architecture Dependency of LLVM bitcode (was Re: compile linux kernel)
On Mon, Sep 29, 2008 at 8:18 AM, Christian Plessl
<christian.plessl at uni-paderborn.de> wrote:
> - Is the architecture dependence of LLVM IR only an artifact of llvm-
> gcc producing architecture dependent results?
No.
It also is an artifact of code compiling architecture and OS dependent
features based on what they detect at configure time
It is an artifact of compiling non-type
2008 Sep 29
5
[LLVMdev] Architecture Dependency of LLVM bitcode (was Re: compile linux kernel)
On 29.09.2008, at 11:53, Jonathan S. Shapiro wrote:
> Watching this thread, it occurs to me that the "V" in "LLVM" is
> creating
> confusion. So far as I know, LLVM is the first project to use
> "virtual"
> to refer to the instruction set of the intermediate form. I understand
> why this labeling made sense (sort of), but it was unfortunate. The