search for: bigendian

...padcheck and --option=socket:testnonblock=True --option=torture:quick=yes -k yes(dc)." ERROR: Testsuite[samba4.rpc.echo on ncacn_ip_tcp with padcheck and --option=socket:testnonblock=True --option=torture:quick=yes -k yes(dc)] REASON: Exit code was 1 == samba4.rpc.echo on ncacn_ip_tcp with bigendian and --option=socket:testnonblock=True --option=torture:quick=yes -k yes(dc) == command: bin/smbtorture --configfile=$SMB_CONF_PATH --maximum-runtime=$SELFTEST_MAXTIME --target=$SELFTEST_TARGET --basedir=$SELFTEST_TMPDIR --option=torture:progress=no --format=subunit --option=torture:quick=yes ncacn_...

...ack-end. -Timo -----Ursprüngliche Nachricht----- Von: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] Im Auftrag von Nick Lewycky Gesendet: Mittwoch, 12. August 2009 04:35 An: LLVM Developers Mailing List Betreff: Re: [LLVMdev] Bug in optimization pass related to strcmp and bigendian back-ends Stripf, Timo wrote: > I thought the LLVM IR is target independent Yes. and that "llvm-gcc -c -emit-llvm -O2" produces target independent code. No. > I'm working on a back-end and use llvm-gcc to first generate the bc file. Afterwards I use llc including the new...

Stripf, Timo wrote: > I thought the LLVM IR is target independent Yes. and that "llvm-gcc -c -emit-llvm -O2" produces target independent code. No. > I'm working on a back-end and use llvm-gcc to first generate the bc file. Afterwards I use llc including the new back-end to produce the assembler file. LLVM IR contains a target-information line but is otherwise target

Stripf, Timo wrote: > I thought the LLVM IR is target independent and that "llvm-gcc -c -emit-llvm -O2" produces target independent code. > > I'm working on a back-end and use llvm-gcc to first generate the bc file. Afterwards I use llc including the new back-end to produce the assembler file. > > -Timo LLVM IR is very target dependent. The IR knows about things

Hi list! Sometimes I need to make boot floppies for an i386 based Linux router. Just for interest, I tried to use syslinux together with my iMac G4 (PPC) with Yellow Dog Linux to create the floppy. I know that this is generally difficult because it requires cross- compiler and cross-assembler. Nevertheless, I tried it because I only needed the disk installer, the loader binaries for i386

...er file. -Timo -----Ursprüngliche Nachricht----- Von: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] Im Auftrag von Eli Friedman Gesendet: Dienstag, 11. August 2009 10:27 An: LLVM Developers Mailing List Betreff: Re: [LLVMdev] Bug in optimization pass related to strcmp and bigendian back-ends On Tue, Aug 11, 2009 at 1:13 AM, Stripf, Timo<Timo.Stripf at itiv.uni-karlsruhe.de> wrote: > On little endian machines the code works correct but on big endian %lhsv > must be compared against 73 << 8. If llvm-gcc thinks it's compiling for a little-endian target, t...

...idate(ad_dc_ntvfs) samba4.rpc.samba3-netlogon on ncacn_np with validate(ad_dc_ntvfs) samba4.rpc.samba3.sharesec on ncacn_np with validate(ad_dc_ntvfs) samba4.rpc.samba3.sharesec on ncacn_ip_tcp with validate(ad_dc_ntvfs) samba4.rpc.samba3.sharesec on ncalrpc with bigendian(ad_dc_ntvfs:local) samba4.rpc.samsync on ncacn_np with bigendian(ad_dc_ntvfs) samba4.rpc.samba3-sessionkey on ncacn_np with bigendian(ad_dc_ntvfs) samba4.rpc.samba3-getusername on ncacn_np with bigendian(ad_dc_ntvfs) samba4.rpc.samba3-lsa on ncacn_np with bigendi...

...ffer format (see bochs_user_framebuffer_create). We still had to add a special register to the virtual hardware so the guest can signal to the host whenever the framebuffer is big endian or little endian (see bochs_hw_init), so both ppc64 and ppc64le guests work properly with the qemu stdvga. So, bigendian guests assume that DRM_FORMAT_XRGB8888 is big endian not little endian. And given that the fourcc codes are used in the userspace/kernel API too (see DRM_IOCTL_MODE_ADDFB2) I think we can't change that any more ... cheers, Gerd

...ffer format (see bochs_user_framebuffer_create). We still had to add a special register to the virtual hardware so the guest can signal to the host whenever the framebuffer is big endian or little endian (see bochs_hw_init), so both ppc64 and ppc64le guests work properly with the qemu stdvga. So, bigendian guests assume that DRM_FORMAT_XRGB8888 is big endian not little endian. And given that the fourcc codes are used in the userspace/kernel API too (see DRM_IOCTL_MODE_ADDFB2) I think we can't change that any more ... cheers, Gerd

...ggenc/audio.c vorbis-tools-1.0/oggenc/audio.c --- vorbis-tools-1.0.orig/oggenc/audio.c Thu Jul 11 16:20:33 2002 +++ vorbis-tools-1.0/oggenc/audio.c Mon Jan 20 09:42:57 2003 @@ -220,6 +220,8 @@ unsigned char buf2[8]; aiff_fmt format; aifffile *aiff = malloc(sizeof(aifffile)); + + unsigned int bigendian = 1; if(buf[11]=='C') aifc=1; @@ -258,6 +260,10 @@ fprintf(stderr, _("Warning: AIFF-C header truncated.\n")); return 0; } + else if( ! memcmp(buffer+18, "sowt", 4) ) + { + bigendian = 0; + } else if(memcmp(buffer+18, "NONE", 4)) {...

Hi all, Does anyone happen to know if there are *any* 32-bit architectures (on which Linux runs) for which the ABI for a "long long" is different from passing two "longs" in the appropriate order, i.e. (hi,lo) for bigendian or (lo,hi) for littleendian? I'd like to switch klibc to use the 64-bit file ABI thoughout, but it's a considerable porting effort, and I'm trying to figure out how to best manage it. -hpa

...hether time.h and sys/time.h may both be included... yes checking for 8-bit clean memcmp... yes checking for vprintf... yes checking for strstr... yes checking for strtod... yes checking for strtol... yes checking for drand48... yes checking for gettimeofday... yes checking whether byte ordering is bigendian... no checking for memory.h... yes checking for ANSI C header files... (cached) yes checking for gcc option to accept ANSI C... checking for function prototypes... yes checking for working const... (cached) yes checking for complex.h... yes checking for malloc.h... yes checking for varargs.h... no...

Lookup format using virtio_gpu_translate_format() instead of hardcoding it. Fixes xorg display on bigendian guests (i.e. ppc64). Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/virtio/virtgpu_gem.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/virtio/virtgpu_gem.c b/drivers/gpu/drm/virtio/virtgpu_gem.c index 336a57f..cc025d8 1006...

Lookup format using virtio_gpu_translate_format() instead of hardcoding it. Fixes xorg display on bigendian guests (i.e. ppc64). Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/virtio/virtgpu_gem.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/virtio/virtgpu_gem.c b/drivers/gpu/drm/virtio/virtgpu_gem.c index 336a57f..cc025d8 1006...

Hello everyone! I've started to implement a ColdFire backend, but there are some troubles during configuring: $ ../llvm/configure --enable-targets=x86,x86_64,coldfire ... ... ... checking whether byte ordering is bigendian... no configure: error: Unrecognized target coldfire configure: error: ../../../llvm/projects/sample/configure failed for projects/sample I've added ColdFire to : 1) TARGETS_TO_BUILD variable 2) 'case "$a_target" in' 3) 'case "$llvm_cv_target_arch" in' 4) ...

Hi, > If yes then this doesnt look all that bad or invasive at first sight (if > the put_user() workaround can be expressed in a cleaner way), but in any > case it would be nice to hear an LLVM person's opinion about roughly when > this is going to be solved in LLVM itself. one thing that seems to be clear to everyone except me is... what are the semantics supposed to be? [My

...is a 64-bit type and "baz" is a 32-bit type, then you functionally have, at least on x86: uint64_t tmp = bar; asm("foo" : "+r" (tmp)); baz = (uint32_t)tmp; One could possibly argue that the latter case should be "baz = (uint32_t)(tmp >> 32);" on a bigendian machine... since this is a gcc syntax it probably should be "whatever gcc does" in that case, as opposed to what might make sense. (I'm afraid I don't have a bigendian box readily available at the moment, so I can't test it out to see what gcc does. I have a powerpc mach...

> I had a similar question ... is the endian-ness of the encoded > speex file, system dependent? or is it always little endian? If it's > always little endian (like the header seems to be) then big endian > machines (or java) will need to map everything to bigendian before > decoding ... Well, wav's are considered little endian but for raw files, there's a command-like switch to specify either little-endian or big-endian (--le and --be). Jean-Marc -- Jean-Marc Valin, M.Sc.A. LABORIUS (http://www.gel.usherb.ca/laborius) Université de She...

No luck there with modifying clang/lib/Basic/Targets.cpp unfortunately. I only modified BigEndian to 'true' and Builder.defineMacro to "__BIG_ENDIAN__" On Sat, Jul 7, 2012 at 2:34 AM, Anton Korobeynikov <anton at korobeynikov.info>wrote: > > Oh sorry, clang. > Then you should modify clang, not backends, look into Basic/Targets.cpp > there. > > PS: Not...

...+0200, Vadim Khoptynets wrote: > Hello everyone! > > I've started to implement a ColdFire backend, but there are some troubles > during configuring: > > $ ../llvm/configure --enable-targets=x86,x86_64,coldfire > ... > ... > ... > checking whether byte ordering is bigendian... no > configure: error: Unrecognized target coldfire > configure: error: ../../../llvm/projects/sample/configure failed for > projects/sample > > I've added ColdFire to : > 1) TARGETS_TO_BUILD variable > 2) 'case "$a_target" in' > 3) 'case "...