| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
|
|
|
| |
tested by beck
|
| |
|
|
|
|
| |
tested by bcallah, proofed by jasper, ok tedu
|
|
|
|
| |
desired semantics. ok deraadt
|
|
|
|
|
|
| |
previous commit.
ok deraadt@
|
|
|
|
|
| |
Now deficient architectures can use this if they need to.
conf/files already tries to pull this in (pointed out by mlarkin)
|
| |
|
|
|
|
| |
checked over by mlarkin
|
|
|
|
|
|
| |
likely to be in the cache (like how the explanation is split between
multiple commits?)
tested by various
|
|
|
|
| |
ok .... I guess noone, because it is summer
|
|
|
|
| |
ok mlarkin tedu
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
for overlapping copies. Attempt to be instruction cache friendly by turning
things around and make memcpy(9) use the forward copy branch of memmove(9),
and implement bcopy(9) by swapping its arguments and dropping into memmove(9).
Same change as the one just made to for hppa.
|
|
|
|
| |
ok kettenis
|
| |
|
|
|
|
|
|
|
|
| |
for overlapping copies. Attempt to be instruction cache friendly by turning
things around and make memcpy(9) use the forward copy branch of memmove(9),
and implement bcopy(9) by swapping its arguments and dropping into memmove(9).
ok deraadt@
|
|
|
|
| |
version.
|
|
|
|
| |
ok kettenis@
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
kgmon(8) to deal with them, this time without public header changes.
Previously various CPUs were iterating over the same global buffer at
the same time to modify it and never ended.
This diff includes some ideas submited by Thor Simon to NetBSD via miod@.
ok deraadt@, mikeb@, haesbaert@
|
|
|
|
| |
at this moment.
|
|
|
|
|
|
|
|
|
| |
various CPUs were iterating over the same global buffer at the same
time to modify it and never ended.
This diff includes some ideas submited by Thor Simon to NetBSD via miod@.
ok mikeb@, haesbaert@
|
|
|
|
| |
in fpsp has to be renamed due to a clash with other parts of the kernel.
|
|
|
|
|
|
|
|
|
| |
right thing for whichever compiler we use.
found while trying to build a profiled kernel on sparc64. solution found
by guenther and refined by miod and kettenis.
ok guenther@ kettenis@
|
| |
|
|
|
|
| |
ok guenther millert kettenis
|
|
|
|
| |
ok deraadt
|
|
|
|
|
|
|
| |
up to 3 times slower than the C code most of the time. This was
brought up by DragonflyBSD guys initially.
ok deraadt, guenther. miod will not miss it.
|
| |
|
|
|
|
| |
getting rid of the (hopefully) last bug in this code.
|
| |
|
| |
|
|
|
|
| |
from bcopy.m4. Fix that.
|
| |
|
|
|
|
|
| |
Also fix the return value of memcpy. With these changes, this seems to
work as advertised now.
|
| |
|
|
|
|
|
|
| |
if the addresses are 4-byte aligned.
ok jsing@
|
|
|
|
| |
from NetBSD. ok miod@ drahn@
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
local registers for a few temporaries. This was changed to use two global
registers. Maybe to permit use in-kernel without conflicting with the
register V7 register window handlers. (Was this done by Chris Torek? Is this
related to Gordon Irlam's work? Or was it in NetBSD? Hard to tell because
NetBSD removed their original cvs tree.)
In V8 the ABI was tightened; more global registers became offlimits in
different ways. We started supporting sun4m, and did not consider this.
As a result, the global registers chosen are the wrong choice. In
particular, %g7 is a poor choice for upcoming TLS work. It looks like
it is safer to use %g5 and %g6 since these functions are "system software".
All re-entrant parts of the system save it.
On sparc64 these functions are in libc per ABI requirement, but are unused.
On sparc, they occur in bootblocks (no reentrancy), kernel (reentrancy saves
globals; kernel is not ABI compliant), userland libc (signal handlers save
globals), and ld.so (symbol binding is not re-entrant on its own).
Discussed rather extensively with guenther, kettenis, miod and drahn.
|
|
|
|
| |
TIMEZONE and DST...
|
|
|
|
|
|
|
| |
unlike normal bzero, we guarantee that the compiler will not optimize out
calls to this function for otherwise dead variables.
to be adjusted as needed when compilers and linkers get smarter.
ok deraadt miod
|
|
|
|
| |
ok djm@, deraadt@
|