File: LocalBits.md

package info (click to toggle)
rust-coreutils 0.7.0-1
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 505,620 kB
  • sloc: ansic: 103,594; asm: 28,570; sh: 8,910; python: 5,581; makefile: 472; cpp: 97; javascript: 72
file content (23 lines) | stat: -rw-r--r-- 1,144 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
# C-Compatible Bit Ordering

This type alias attempts to match the bitfield ordering used by GCC on your
target. The C standard permits ordering of single-bit bitfields in a structure
to be implementation-defined, and GCC has been observed to use Lsb0-ordering on
little-endian processors and Msb0-ordering on big-endian processors.

This has two important caveats:

- ordering of bits in an element is **completely** independent of the ordering
  of constituent bytes in memory. These have nothing to do with each other in
  any way. See [the user guide][0] for more information on memory
  representation.
- GCC wide bitfields on big-endian targets behave as `<T, Lsb0>` bit-slices
  using the `_be` variants of `BitField` accessors. They do not match `Msb0`
  bit-wise ordering.

This type is provided solely as a convenience for narrow use cases that *may*
match GCC’s `std::bitset<N>`. It makes no guarantee about what C compilers for
your target actually do, and you will need to do your own investigation if you
are exchanging a single buffer across FFI in this manner.

[0]: https://bitvecto-rs.github.io/bitvec/memory-representation