search for: endiannes

...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 safe languages. It is an artifact of system headers including inline asm. It is an artifact of the endianness of the system. > - What architecture-specific features are present in the IR that > prevent running the same LLVM bitcode on different architectures? A better question is: what architecture-abstracting features would make writing target independent LLVM bitcode easier? There is 1 that I t...

Hello! I am trying to read Ferret index files from Windows machine on my Mac G5 Leopard machine, but the following returns nil: Ferret::Index::IndexReader.new( index_paths ) Should this work? Are index files guaranteed to be platform independent or not? Is there any problem if files (top direectory) are renamed? izidor P.S. I can create the index myself and then everything works.

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

> hton and ntoh intrinsics. These are needed to allow target code to > deal with endianness in a target independent way. (Ok, you could > 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 file...

...these just allow reading and writing raw bytes. To handle > reading and writing semantic data, there are two additional classes. > *ThinStreamReader* and *ThinStreamWriter.* > > These accept any subclass of `ThinStream` and maintain an offset and allow > you to read integers in any endianness, strings, objects, arrays of objects > (both fixed length records and variable length records), and various other > things. > > Finally, there are *ThinStreamRef* and *WritableThinStreamRef* which you > can think of as `ArrayRef` and `MutableArrayRef` for ThinStreams. They > all...