Am 28.02.2018 um 16:40 schrieb Michel Dänzer:
On 2018-02-28 04:25 PM, Christian König wrote:
Am 28.02.2018 um 16:21 schrieb Michel Dänzer:
On 2018-02-28 03:41 PM, Christian König wrote:
The 32bit address range end is exclusive, not inclusive.
The other way around. :) Inclusive means [a,b], i.e. an interval
including the endpoints, whereas exclusive means ]a,b[, i.e. an interval
not including the endpoints. The patch changes the 32-bit address range
endpoint from exclusive to inclusive.
Actually that's not what I meant. How about this:
"The range is stored as exclusive, not inclusive. Subtracts one to get
the inclusive interval for the calculation."
Sounds good to me, but I'll defer to native English speakers for the
final verdict.
Since this is an important bug fix I'm going to commit it as long as
nobody speaks up in the next two hours or so.
Christian.
_______________________________________________
amd-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
