> On Feb 24, 2019, at 8:22 AM, David Holland <[email protected]> wrote: > > Given that the predominant use of these is to fetch from user-supplied > pointers, which can be crap, it would best to include an alignment > check; otherwise ~all call sites will require explicit checks, which > in addition to being error-prone start running into annoying > portability questions.
Great suggestion, and you know, this gives me an idea — the arch-specific back-ends can get a different name, and the API contract logic like this can go in subr_copy.c, along with the convenience aliases that I wanted to do originally. -- thorpej
