search for: __little_endian__

...to a patch I submitted a little while ago (still pending): > http://llvm-reviews.chandlerc.com/D2760 > > If accepted, would it make this patch (and a others) unnecessary? Hi Robert, It is, but hijacking your patch a little, why not use __ORDER_LITTLE_ENDIAN__? Why do we need to create __LITTLE_ENDIAN__ ? cheers, --renato

...anguages, it would be very useful. If you're just trying to *reduce* the endianness assumptions that leak through, I don't think it's a good approach. There is just no way to solve this problem with C. By the time the preprocessor has run, your C code has already had #ifdef __LITTLE_ENDIAN__ etc evaluated, for example. How do you propose to handle things like: struct foo { #ifdef __LITTLE_ENDIAN__ int x, y; #else int y, x; #endif }; -Chris

it seems that this check does not work on solaris #if BYTE_ORDER != LITTLE_ENDIAN #define BYTE_SWAP #endif could you please check that BYTE_SWAP is defined in rijndael.c -m

...uary 2014 18:32, Daniel Dunbar <daniel at zuster.org> wrote: > $(error "ENDIAN is $ENDIAN"), before and after the include of > Makefile.config and Makefile.singlesrc (which includes Makefile.programs). Hi Daniel, Thanks, that did the trick! ;) In TargetConfig.mk.in: #ifdef __LITTLE_ENDIAN__ ENDIAN := little #else ENDIAN := big #endif Seems like it should be __ORDER_LITTLE_ENDIAN__ to be cross-platform. Attaching the patch that adds aarch64 (which is identical to the one applied in LLVM a few days ago) to the config plus change the TargetConfig.mk. Shouldn't cause too much distu...

Hi, I'd like to use LLVM to compile and optimise code when I don't know whether the target CPU is big- or little-endian. This would allow me to create a single optimised LLVM bitcode binary of an application, and then run it through a JIT compiler on systems of differening endianness. I realise that in general the LLVM IR depends on various characteristics of the target; I'd just

Hi all, Speex currently decides endianness at configure-time. This causes the ppc half of Mac universal binaries to have some endianness problems. Most notably, the header built by speex_packet_to_header() has incorrect byte-ordering. This Apple developer page describes the incantation that can be used to build universal binaries on Mac. It also highlights the configure-time versus compile-time

..._ENDIAN__) || !defined(COMPILE_TIME_ENDIANESS) && defined(WORDS_BIGENDIAN) /* do big endian thing */ #else /* do little endian thing */ #endif This seems excessively complicated, so I preferred not to do it. Can others comment on the availability of the compiler defined __BIG_ENDIAN__ and __LITTLE_ENDIAN__ variables? Pete

On 24 February 2014 17:02, Daniel Dunbar <daniel at zuster.org> wrote: > Nothing in particular springs to mind. Is it possible that in the context > where this part of the Makefile is running Makefile.config isn't available? This is a standard lnt run, create in the same way I ran for x86_64 and ARM, so I'm not sure what could be wrong. > I'm not sure how this can be

...the llvm part of this is more straightforward and less controversial than the llvm-gcc part. Maybe I should submit the llvm part (since it applies to all source languages) and keep the llvm-gcc part as a local hack. > How do you propose to handle things like: > > struct foo { > #ifdef __LITTLE_ENDIAN__ > int x, y; > #else > int y, x; > #endif > }; I can't make all C programs work regardless of target endianness. This one will only work on little-endian: int x = 1; assert(*(char *)&x == 1); You've just highlighted another restriction that I'll have to impo...

Hi, Is the http://xenbits.xensource.com/linux-2.6-xen.hg tree still being updated? if not, what''s the preferred Linux tree to track that has all of the Xen bits? Thanks, Muli _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel