#
5b3646a9 |
| 17-Feb-2020 |
Matthew Dillon <dillon@apollo.backplane.com> |
kernel and world - Replace bcmp/bcopy/bzero/memcmp/memcpy/memmove/memset
* Replace bcmp/bcopy/bzero/memcmp/memcpy/memmove/memset with mjg's code, with some minor adjustments.
* mjg's code has bee
kernel and world - Replace bcmp/bcopy/bzero/memcmp/memcpy/memmove/memset
* Replace bcmp/bcopy/bzero/memcmp/memcpy/memmove/memset with mjg's code, with some minor adjustments.
* mjg's code has been given its own header file, <machine/asm_mjgmacros.h>
* Also replaces copyin and copyout.
* Around a 1.7% improvement in bulk-build performance.
show more ...
|
#
83d15e57 |
| 28-Mar-2019 |
Matthew Dillon <dillon@apollo.backplane.com> |
kernel - make bcmp linux-compatible, add memcmp world - make bcmp linux-compatible
* Make bcmp and memcmp the same. Our bcmp() was returning 0 or 1 (not subtracting the last byte), which is comp
kernel - make bcmp linux-compatible, add memcmp world - make bcmp linux-compatible
* Make bcmp and memcmp the same. Our bcmp() was returning 0 or 1 (not subtracting the last byte), which is compatible with the manual page but it isn't what linux does.
* It also looks like memcmp is sometimes turned into bcmp by the compiler (?), at least when compiling the kernel, so we don't want to break that either.
* Add memcmp to the kernel build, synchronize both memcmp and bcmp from libc.
* This makes our bcmp compatible with linux.
show more ...
|
#
8b927cb7 |
| 05-Sep-2015 |
John Marino <draco@marino.st> |
libc/x86-64: Add GNU-stack ELF notes to many assembly files
Most of the assembly files in libc/x86-64 were missing GNU-stack ELF notes (they never had them) which means libc and every program that l
libc/x86-64: Add GNU-stack ELF notes to many assembly files
Most of the assembly files in libc/x86-64 were missing GNU-stack ELF notes (they never had them) which means libc and every program that links with it has required an executable stack. I need to determine a way to check which object files are missing this section and make sure every single libc object file is covered.
show more ...
|
#
b2b3ffcd |
| 04-Nov-2009 |
Simon Schubert <corecode@dragonflybsd.org> |
rename amd64 architecture to x86_64
The rest of the world seems to call amd64 x86_64. Bite the bullet and rename all of the architecture files and references. This will hopefully make pkgsrc build
rename amd64 architecture to x86_64
The rest of the world seems to call amd64 x86_64. Bite the bullet and rename all of the architecture files and references. This will hopefully make pkgsrc builds less painful.
Discussed-with: dillon@
show more ...
|
#
3f3709c3 |
| 07-Nov-2009 |
Jordan Gordeev <jgordeev@dir.bg> |
Revert "rename amd64 architecture to x86_64"
This reverts commit c1543a890188d397acca9fe7f76bcd982481a763.
I'm reverting it because: 1) the change didn't get properly discussed 2) it was based on
Revert "rename amd64 architecture to x86_64"
This reverts commit c1543a890188d397acca9fe7f76bcd982481a763.
I'm reverting it because: 1) the change didn't get properly discussed 2) it was based on false premises: "The rest of the world seems to call amd64 x86_64." 3) no pkgsrc bulk build was done to test the change 4) the original committer acted irresponsibly by committing such a big change just before going on vacation.
show more ...
|
#
c1543a89 |
| 04-Nov-2009 |
Simon Schubert <corecode@dragonflybsd.org> |
rename amd64 architecture to x86_64
The rest of the world seems to call amd64 x86_64. Bite the bullet and rename all of the architecture files and references. This will hopefully make pkgsrc build
rename amd64 architecture to x86_64
The rest of the world seems to call amd64 x86_64. Bite the bullet and rename all of the architecture files and references. This will hopefully make pkgsrc builds less painful.
Discussed-with: dillon@
show more ...
|