On 05/17/2018 08:57 AM, Peter Maydell wrote: > This looks right for element sizes up to 8, but I don't understand > how it handles 16 byte elements as the commit message says -- the > d[0] and d[1] are the wrong way round and don't form a single > 16-byte big-endian value, so they must need special casing somewhere > else ?
You're right that it's not a proper int128 for host arithmetic. Fortunately, the only operation we have on 128-bit values, at present, is move. How better might you word the commit message? r~
