-
These are currently broken because the order of elements inside vectors is reversed on big-endian systems: the ARM ABI requires that element 0 is located at the highest address of the vector type. How…
-
It's not currently possible to specify the endianness of the target architecture, which could lead to confusion for datatypes larger than it's #bits size.
-
All the `#[repr(C)]` structs implement Pread/Pwrite but do not implement Cread/Cwrite which is useful in no_std environments.
I'd be happy to implement Cread/Cwrite for the ELF structs (with tests)…
-
Right now there is no decided endianness or architecture decided for the representation of the V4L2 structures used on virtqueues.
Architecture is rather obvious, 64-bit V4L2 headers should be used…
-
Consider `endian3.c`:
```c
#include
#include
struct S {
#if __BYTE_ORDER == __LITTLE_ENDIAN
unsigned b : 12;
unsigned a : 12;
#else
unsigned a : 12;
unsigned b : 12;
#endif
};
i…
-
Hi Guys,
I opened the same issue to the wrong place in the riscv-c-api-doc. So I open a new one here.
We get the GNU binutils patches from Marcus Comstedt recently, to support RISCV big endian …
-
HFST's binary formats are not endian-neutral, which is a quite big issue. I'm looking into how to best fix this, which may result in a breaking change of the binary formats. I've got a PowerPC chroot …
-
it seems that this emulator is only suitable for little endian systems.
Can you make the emulator endian-independent?
-
I implemented the modbus library into my project and noticed while debugging that the union CRC_t, MbDataField is endian dependent. It would really help if the dependence on endianness would be docume…
-
I propose to encode endianness in format:
```
e(_?[bl]\d+)+
```
where
* `e` is for `endianness`;
* `[bl]` are for endianness types (big or little);
* `\d+` is for group size (by default 8 bits,…