search for: d61725

Displaying 3 results from an estimated 3 matches for "d61725".

2019 May 09
3
RFC: On removing magic numbers assuming 8-bit bytes
..."addressable unit", we've been thinking a bit and are leaning toward staying with the prevalent "byte" terminology for as long as upstream is 8-bit-only to avoid mixed terminology or larger patches. However, we're flexible on this, and I've uploaded a twin patch (in D61725) to my original showcase showing how "addressable unit" could look. > > > > > Active contribution from > > > the sponsors in other areas would also be a key factor. > > > > I'm not sure how to interpret that, but our team here at Ericsson >...
2019 May 09
3
RFC: On removing magic numbers assuming 8-bit bytes
...nit", we've been thinking a bit and are > leaning toward staying with the prevalent "byte" terminology for as > long as upstream is 8-bit-only to avoid mixed terminology or larger > patches. However, we're flexible on this, and I've uploaded a twin > patch (in D61725) to my original showcase showing how "addressable > unit" could look. > > > Active contribution from > the sponsors in other areas would also be a key factor. > > > I'm not sure how to interpret that, but our team here at Ericsson > is > fairly large, we...
2019 May 08
2
RFC: On removing magic numbers assuming 8-bit bytes
On Mon, 2019-05-06 at 15:56 -0700, Philip Reames via llvm-dev wrote: > > > On 5/6/19 2:43 AM, Tim Northover via llvm-dev wrote: > > On Mon, 6 May 2019 at 10:13, James Courtier-Dutton via llvm-dev > > <llvm-dev at lists.llvm.org> wrote: > > > Although the above is mentioning bytes, looking at the "/ > > > 8" and "& 0x7" makes