The previous version was very broken; SIZEOF_* seem like LP64, even
though this should be, and had been configured for n32 userland.
May fix random build failures reported as PR toolchain/57241.
XXX
There still remain oddies. mknative again soon with update for
configure scripts.
Conserve tp register for _UC_CPU and update later if _UC_TLSBASE is
specified. This is what powerpc does, which also uses a general
purpose register for TLS pointer.
Found by tests/lib/libpthread/t_swapcontext:swapcontext1, which
successfully passes now.
Since its size must be determined a priori, explicitly use
c.ebreak for sure.
Now, related tests in ATF successfully pass for riscv64,
as far as I can see.
It cannot fit within 18 bytes, of course ;)
As we had never provided working bpf(4) implementation for LP64
userland on mips, just use natural structure size here.
references internal symbols in libcrypto like ossl_dh_compute_key which
have been made static by the linker script (they are still visible in the
archive version).
It was broken since rev 1.21 24 years ago, and got more broken code later on:
remove leftover device_xname(sc->sc_dev) param from aprint_debug_dev in one block.
fix wrong method name devoce_xname to device_xname in second block.
rename et to eh for consistency, and define it (definition was removed in the past).
while here, improve the code with riastradh help to make it safer.
pullup to at least netbsd-10 is needed.
netbsd-core.c is for the old-style core format, which has
never been used for riscv.
Note that:
- binutils/bfd does not use this file for riscv.
- Up-to-date core file format is supported by elf.c.
It does not longer output redundant `` (ipip-proto-4)'':
cba9b77a98
Now, these tests become passing again.
Thanks mlelstv@ for finding out upstream commit.
OK ozaki-r@
Nor is it a bug that they're applied to the file rather than stored in
some magic secret database where they survive reinstalls, which the
prior wording seems to suggest was the eventual intention.
It is worth noting that they change the target file, so still say that.
Debug lists are probably still wrong, though -- looks like there's no
rule to change h_inotify_*.out.debug to h_inotify_*.debug. Out of
energy to look into this further, though; please fix me!