Notes at offset 0x00000128 with length 0x00000018:
Owner Data size Description
NetBSD 0x00000004 IDENT 699002300 (6.99.23)
Notes at offset 0x00000154 with length 0x00000020:
Owner Data size Description
NetBSD 0x00000009 MARCH <earmv7hf>
that we can find their version from verdef not vertree. This bug
showed up on the hp700 build of heimdal's libkrb5, where we got
the "end" symbol with a bad version from libhx509. The hp700 linker
script defines that end symbol.
reality. Recognize old PT___GETREGS40 (for struct __reg40 without
GBR). Recognize PT_GETFPREGS that we don't yet actually have, but for
which the number is now reserved.
When -Bsymbolic, all resolved symbols need to be created with relative
relocations. The dynamic linker depends on that because it only
knows how to perform relative relocations in the first pass to
relocate itself. This bug ended up creating R_SPARC_64 symbols for
12 relocation symbols in ld.elf_so, one of them dlopen(), which
ended up breaking things using dlopen(), most notably PAM.
-mfix-loongson2f-btb, to avoid a gas warning "macro expanded into
multiple instructions" (which cause GDIUM kernel build failure
as it's built with -Wa,-mfix-loongson2f-jump -Wa,--fatal-warnings).
This works around a bug in the branch prediction logic of the
CPU which can cause a hard hang. The existing fix-loongson2f-jump
works around the same bug, but by 'fixing' the jump target to be within the
same 256MB region as the kernel. This will (silently) cause a jump
to the wrong address if the jump is intentionally to some other
region (e.g. a call to pmon).
fix-loongson2f-btb instead works around the issue by adding an explicit flush
of the branch target buffer (via a write to a cop0 register) before every
jump register instruction.
fire before a jump to a zero or "near" zero address. This can't be used
with MIPS1 kernels since MIPS1 doesn't have a trap instruction (it will
be silently ignored).
