the etc Makefile override that by putting USETOOLS into $.MAKEOVERRIDES
This way the default for kernel compiles is still to use the installed
toolchain instead of depending on $TOOLDIR. $TOOLDIR can be used by
simply adding USETOOLS=yes to the command line as usual.
Adjust each ports template to set the default no setting and also pull in
bsd.own.mk if they weren't already to ensure they'll build correctly
with the new toolchain setup.
This will allow improvements to the pmaps so that they can more easily defer expensive operations, eg tlb/cache flush, til the last possible moment.
Currently this is a no-op on most platforms, so they should see no difference.
Reviewed by Jason.
option for System V semaphores. It appears that there are no overrides
in the code and each file has the following added.
options SYSVSEM # System V semaphores
+#options SEMMNI=10 # number of semaphore identifiers
+#options SEMMNS=60 # number of semaphores in system
+#options SEMUME=10 # max number of undo entries per process
+#options SEMMNU=30 # number of undo structures in system
options SYSVSHM # System V shared memory
If anyone thinks that this is incorrect for any of these files, please
correct it.
Note - the i386 port was not forgotten. It was done separately.
same file. No other changes, OpenBSD log messages below.
> More EMODD work:
> - Using CVTDL and subtracting to seperate integer from fraction does
> not work if the integer is >32 bits long; instead, rearrange the bits
> into a quadword, use ASHQ to truncate, and then subtract.
>
> Also:
> - Set the condition codes properly; this fixes the other problem with
> >32-bit-integer parts in libm by letting modf subtract the fractional
> part (which *is* a double) to get the integral part in a double.
> - move the zero checks earlier in the routine
>
> - instead of 'ret' in zeroexit, use brw goback
> Switch a "BGTR foo" to a "BLSS bar; BRW foo; bar:". In this case, the
> difference between the BGTR and foo: is too large for a byte displacement.
> as should give an error or at least a warning here, but it doesn't;
> instead it merrily outputs a completely bogus displacement.
> This fixes problems with EMODD on numbers with negative exponents.
>