Displaying 3 results from an estimated 3 matches for "fwiu".
Did you mean:
fwip
2019 Jul 12
2
Introducing an Alignment object in LLVM
Alignment in LLVM is currently represented with an `unsigned`, sometimes an
`uint32_t`, `uint64_t` or `uint16_t`.
FWIU the value has the following possible semantics:
- 0 means alignment is unknown,
- 1 means no alignment requirement,
- a power of two means a required alignment in bytes.
Using `unsigned` throughout the codebase has several disadvantages:
- comparing alignments may compare different things, wha...
2019 Jul 12
2
Introducing an Alignment object in LLVM
...ed, remove the
> implicit conversions.
>
>
> On Jul 12, 2019, at 2:20 AM, Guillaume Chatelet via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
> Alignment in LLVM is currently represented with an `unsigned`, sometimes
> an `uint32_t`, `uint64_t` or `uint16_t`.
> FWIU the value has the following possible semantics:
> - 0 means alignment is unknown,
> - 1 means no alignment requirement,
> - a power of two means a required alignment in bytes.
>
> Using `unsigned` throughout the codebase has several disadvantages:
> - comparing alignments may...
2016 Oct 22
29
[Bug 98386] New: [NVE7] bus: MMIO write of FAULT at [ IBUS ], Pointer to {TDMS, flat panel) table invalid
https://bugs.freedesktop.org/show_bug.cgi?id=98386
Bug ID: 98386
Summary: [NVE7] bus: MMIO write of FAULT at [ IBUS ], Pointer
to {TDMS,flat panel) table invalid
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: minor
Priority: