search for: endianess

Hi, As a first step to port the LLVM chain on an in-house big-endian processor, I'm integrating the native assembler as a new '-assemble -arch=' in llvm-mc. All work quite well, I have a correct output ELF format except that generated code is little-endian. I've understood that the endianess of the LLVM chain is controlled by the DataLayout class, but it appear to me that llvm-mc does not make use of such class. I've seen a backend (CPU0, http://jonathan2251.github.io/lbd/genobj.html) that defines two different targets and performs the byte swapping as part of the 'EmitInstruc...

With this we try to detect if the endianess switch works and assume LE if not. Suggested by Ben. Fixes: 51c05340e407 ("drm/nouveau/device: detect if changing endianness failed") --- .../gpu/drm/nouveau/nvkm/engine/device/base.c | 39 ++++++++++++------- 1 file changed, 26 insertions(+), 13 deletions(-) diff --git a/drivers/gpu/d...

On Tue, Oct 13, 2020 at 8:01 AM Karol Herbst <kherbst at redhat.com> wrote: > > With this we try to detect if the endianess switch works and assume LE if > not. Suggested by Ben. > > Fixes: 51c05340e407 ("drm/nouveau/device: detect if changing endianness failed") > --- > .../gpu/drm/nouveau/nvkm/engine/device/base.c | 39 ++++++++++++------- > 1 file changed, 26 insertions(+), 13 deletions(-...

Hello, I'm running a Squid cache (Version 3.1.10) on CentOS 6.6 as a forward proxy which is reachable over a global IPv6 address. For whatever reason, Squid tries to perform PTR lookups on the client's IPv6 address. The weird thing is, that Squid seems to struggle with the "endianess" of the IPv6 address blocks. For example: My current client IP is 2003:6e:d79:2104:7163:7ecd:9333:f0be. Squid tries to resolve b.e.f.0.3.3.9.3.c.d.7.e.6.3.7.1.0.4.2.1.7.9.0.d.6.e.0.0.0.3.2.0.ip6.arpa. That means: b.e.f.0.3.3.9.3.c.d.7.e.6.3.7.1.0.4.2.1.7.9.0.d.6.e.0.0.0.3.2.0.ip6.arpa -&...

...source code of jspeex i see that when i pass pcm data as a parameter to SpeexEncoder.processData they use it as little endian and convert it to a float[] and only then the data is encoded to a byte[] of speex samples. I'm only getting noise on the flash client side, and i though it could be an endianess problem, doesn anyone have any suggetion? I'm recording the pcm16bit data to a raw file and when i play it, i have lots of noise. I also record the speex data to a raw file but i can't find a way to play it, any hint? Thank you -------------- next part -------------- An HTML attachment wa...

Since commit 72e61eb40b55dd57031ec5971e810649f82b0259 (virtio: change config to guest endian) config space is no longer fixed endian. Lets change the virtio_blk_config variables. Signed-off-by: Christian Borntraeger <borntraeger at de.ibm.com> --- include/linux/virtio_blk.h | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) Index: kvm/include/linux/virtio_blk.h

Jean-Marc, It appears that since testcelt reads a WAVE file from disck and passes the data directly to celt_encode, so that celt_encode's "in" buffer must be expecting little-endian formatted packets. Is this correct? Is there endiness switch somewhere? Thx MikeH -------------- next part -------------- An HTML attachment was scrubbed... URL:

Provide helper functions that convert from/to LE for virtio devices that are not operating in legacy mode. We check for the VERSION_1 feature bit to determine that. Based on original patches by Rusty Russell and Thomas Huth. Reviewed-by: David Hildenbrand <dahi at linux.vnet.ibm.com> Signed-off-by: Cornelia Huck <cornelia.huck at de.ibm.com> --- drivers/virtio/virtio.c |

Provide helper functions that convert from/to LE for virtio devices that are not operating in legacy mode. We check for the VERSION_1 feature bit to determine that. Based on original patches by Rusty Russell and Thomas Huth. Reviewed-by: David Hildenbrand <dahi at linux.vnet.ibm.com> Signed-off-by: Cornelia Huck <cornelia.huck at de.ibm.com> --- drivers/virtio/virtio.c |

...been digging into the problem with the > null_deref test today but I was unable to clearly identify the > problem. I suspect that it was either a bug with the calling > convention/unwinding that lead to the flags() pointer to get > corrupted. It is also possible that it was related with endianess > issues caused by some bug in the pointer arithmetic inserted by the > sanitizer code (there are many type and bit casts which makes hard to > follow the > references). I decided to upgrade the compiler I was using to build > clang which made the problem with this testcase to go a...

...t;linux/libnvdimm.h> > +#include <linux/spinlock.h> > + > +struct virtio_pmem_request { > + /* Host return status corresponding to flush request */ > + int ret; > + > + /* command name*/ > + char name[16]; So ... why are we sending string commands and expect native-endianess integers and don't define a proper request/response structure + request types in include/uapi/linux/virtio_pmem.h like struct virtio_pmem_resp { __virtio32 ret; } #define VIRTIO_PMEM_REQ_TYPE_FLUSH 1 struct virtio_pmem_req { __virtio16 type; } ... and this way we also define a proper endia...

...t;linux/libnvdimm.h> > +#include <linux/spinlock.h> > + > +struct virtio_pmem_request { > + /* Host return status corresponding to flush request */ > + int ret; > + > + /* command name*/ > + char name[16]; So ... why are we sending string commands and expect native-endianess integers and don't define a proper request/response structure + request types in include/uapi/linux/virtio_pmem.h like struct virtio_pmem_resp { __virtio32 ret; } #define VIRTIO_PMEM_REQ_TYPE_FLUSH 1 struct virtio_pmem_req { __virtio16 type; } ... and this way we also define a proper endia...

On Mon, 22 Oct 2007, Dale Johannesen wrote: > In principle I think keeping IEEE float and double in an endian- > independent form in the IR files is a good idea. BUT: I'm told > retaining the ability to use files in the existing format is a > requirement (so floats still need to occupy 8 bytes). Since ARM target > doesn't currently work that one is a reasonable

One possibility is that Lame is using the wrong endianess for your system try changing NUMBER_LITTLE_ENDIAN to NUMBER_BIG_ENDIAN in liveice.h and rebuilding. The default distribution of Lame uses big endia samples on IO, which means that in raw input mode it needs the -x arg to be set. However - some 'helpful' people have made this the default on...

...to use Dan Kegel's crosstool to build a regular gcc toolchain. This will give you binutils, libgcc, and glibc, which you will need anyway. Building llvm-gcc was relatively painless. The only problem I've encountered was that my target had no hardware floating point support and the endianess for the softfloat implementation (libgcc) differed from integer endianess, which required some patches at the llvm side. I have not checked if this is still necessary. If you run into the same problems, I would be happy to share the patch (which I have updated to llvm 2.4 at some point). -...

...e to hear their experiences. If any ARM/GCC experts know how to fix arm.md to not refer to Darwin-specific macros, that would be great, too. Building llvm-gcc was relatively painless. The only problem I've > encountered was that my target had no hardware floating point support > and the endianess for the softfloat implementation (libgcc) differed > from integer endianess, which required some patches at the llvm side. > I have not checked if this is still necessary. If you run into the > same problems, I would be happy to share the patch (which I have > updated to llvm 2.4 at som...

...rsal 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 endianess problem http://developer.apple.com/documentation/Porting/Conceptual/PortingUnix/compiling/chapter_4_section_3.html I have included a patch that applies Apple's recommendation to use the gcc-defined __BIG_ENDIAN__ preprocessor variable to determine endianness at compile-time. This technique wo...

...current place to fix up the instructions (EncodeInstruction) is too early and misses the final expression fixups. I also continue to struggle in the lib/Target/<local target>/MCTargetDesc area to get clean, easy and elegant access to the environment such as chip/instruction variants let alone endianess. Finally, I still shouldn't be worrying about endianess at that level. The text and data should be marked for element sizes and the endian bit twiddling should happen at a higher lever just before final output. The person like me working on a specific target shouldn't have to do this. Ther...

Note that I've set the SA_NODEFER flag for the SEGV handler in the ASan runtime only a couple of days ago. Not sure that could've affected this test though; without that flag the second SEGV would've simply crashed the program. But you can try removing the flag from compiler-rt/trunk/lib/sanitizer_common/sanitizer_posix_libcdep.cc and see if that makes any difference. HTH, Alex On

...been digging into the problem with the > null_deref test today but I was unable to clearly identify the problem. I > suspect that it was either a bug with the calling convention/unwinding that > lead to the flags() pointer to get corrupted. It is also possible that it > was related with endianess issues caused by some bug in the pointer > arithmetic inserted by the sanitizer code (there are many type and bit > casts which makes hard to follow the references). I decided to upgrade the > compiler I was using to build clang which made the problem with this > testcase to go away (!)...