What we really need to do is to make bcopy a wrapper around memmove on all architectures, not just some. It's this lack of uniformity that's causing problems. Warner On Sun, May 6, 2018 at 4:32 PM, Conrad Meyer <cem_at_freebsd.org> wrote: > The same change as for powerpc needs to be made for riscv — the > (bcopy) trick — to avoid expansion. > > Best, > Conrad > > P.S., Mark, your email server is misconfigured and most/all of your > emails get flagged as spam. I only saw this because I occasionally > check the spam folder. > > On Sat, May 5, 2018 at 4:39 PM, Mark Millard <marklmi26-fbsd_at_yahoo.com> > wrote: > > --- bcopy.o --- > > In file included from /workspace/src/sys/riscv/riscv/bcopy.c:39:0: > > /workspace/src/sys/sys/systm.h:262:31: error: expected identifier or > '(' before '{' token > > #define bcopy(from, to, len) ({ \ > > ^ > > /workspace/src/sys/riscv/riscv/bcopy.c:134:1: note: in expansion of > macro 'bcopy' > > bcopy(const void *src0, void *dst0, size_t length) > > ^~~~~ > _______________________________________________ > freebsd-current_at_freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org" >Received on Sun May 06 2018 - 20:58:30 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:15 UTC