| Age | Commit message (Collapse) | Author |
|---|
|
as suggested by miod.
ok miod@
|
|
|
|
ok kettenis@
|
|
|
|
file load if necessary. Will be used very shortly.
|
|
was breaking non GNUC defining compilers.
Came up during a conversation with ragge@, positive
comments from several.
|
|
unmaintainable). these days, people use source. these id's do not provide
any benefit, and do hurt the small install media
(the 33,000 line diff is essentially mechanical)
ok with the idea millert, ok dms
|
|
traditionnaly found in libkern. However, the memcmp() flavour would behave
as bcmp() with only two possible return values: zero and positive non-zero.
This broke the name cache RB trees which now rely upon proper memcmp()
semantics(negative value, zero, or positive value).
Just give up on these macros and provide the same code as libc, in libkern.
As a side effect, this no longer uses the cmpc3 instruction, which is not
implemented and requires (slow) kernel emulation, on the original uVax.
|
|
|
|
and to override the way HEAP_START and HEAP_LIMIT are defined.
|
|
According to RFC1350 there should be always be a terminating NUL.
Andre Gillibert on bugs@ pointed out that the misformed packets
caused Gentoo Linux's tftpd (atftpd) to crash trying to transfer
pxeboot to an OpenBSD machine.
This is slightly different diff than the one proposed by Andre, but
he confirms it also fixes the problem.
"looks like a better diff to me" deraadt@.
|
|
ok form@ kettenis@
|
|
won't be allocated. Check for this in close() so as not to free() bogus
pointers.
|
|
which are uniform for the profclock on each cpu in a SMP system (but using
a different seed for each cpu). on all cpus, avoid seeding with a value out
of the [0, 2^31-1] range (since that is not stable)
ok kettenis drahn
|
|
has never been performance sensitive.
Running on all platforms, discussed with millert and kettenis, ok toby
|
|
long ints for alpha. we've got only one instruction (cvttq) to
convert double-t to quadword, and float64_to_int64 did not take
into account the unsigned conversions
therefore, overflow always occured, and half of the unsigned range
(LONG_MAX .. ULONG_MAX) was broken
introduce roundAndPackInt64NoOverflow and float64_to_int64_no_overflow
for softfloat, that works with unsigned integers as well. note
that this will return zero for nan/inf/oflow/uflow, raising exception
flag
perl is happy now
looked over by miod@
tested by naddy@, and by me on nick@'s alpha
|
|
Not sure what's more surprising: how long it took for NetBSD to
catch up to the rest of the BSDs (including UCB), or the amount of
code that NetBSD has claimed for itself without attributing to the
actual authors.
OK deraadt@
|
|
|
|
|
|
ELF image being loaded.
ok miod@
|
|
|
|
including mulscc to do multiplications) and switch to the generic random.c
code.
|
|
various segments. Hopefully this will help remove various
hacks in the boot loader in the future. This should have no
effect on most architectures (as we tend to have LMA == VMA).
ok drahn@, soft ok's various others.
|
|
|
|
|
|
|
|
from brynet@gmail.com
|
|
the hp300 related ones currently in use. CN_NORMAL becomes CN_LOWPRI,
CN_INTERNAL becomes CN_MIDPRI and CN_REMOTE becomes CN_HIGHPRI.
ok miod@
|
|
boot code uses 32-bit blknos anyway
|
|
on m88k.
|
|
in files.alpha to compensate for NO_IEEE kernels.
This will allow the softfloat code to be used by other platforms than alpha.
|
|
|
|
with bcopy.S
ok miod@
|
|
|
|
directive can select between MI and MD versions of these files. At
the same time, adjust the boot programs to pick exactly what they need,
instead of the 7 or 8 mechanisms previously used.
There will be some fallout from this, but testing it all by myself is a
ridiculously slow process; it will be finished in-tree.
Various developers were very nice and avoided making fun of me when I
was gibbering in the corner..
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
from hppa the fact that t1-t4 actually number down from r22-r19 got somehow
lost.
|
|
No change in generated code.
|
|
and" at the same time).
|
|
both 32- and 64-bit versions can be created (previously only one or the
other could be built for a given boot loader).
Use this to allow the i386 and amd64 boot blocks to boot both ELF32 and
ELF64 kernels (i.e. amd64 boot blocks can now load i386 kernels, and
vice versa). Obviously the system must support LONG mode in order to
successfully run the amd64 kernel once it is loaded.
Advice and discussions from/with dale@ (going back three years). Much
testing nick@ and todd@; thanks.
|
|
|
|
input from miod@, ok kettenis@
|
|
|
