|
Revision tags: v6.2.1, v6.2.0, v6.3.0, v6.0.1, v6.0.0, v6.0.0rc1, v6.1.0, v5.8.3, v5.8.2, v5.8.1, v5.8.0 |
|
| #
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 ...
|
|
Revision tags: v5.9.0, v5.8.0rc1, v5.6.3, v5.6.2, v5.6.1, v5.6.0, v5.6.0rc1, v5.7.0, v5.4.3, v5.4.2, v5.4.1, v5.4.0, v5.5.0, v5.4.0rc1, v5.2.2, v5.2.1 |
|
| #
5d48b312 |
| 06-May-2018 |
Matthew Dillon <dillon@apollo.backplane.com> |
kernel - Refactor bcmp, bcopy, bzero, memset
* For now continue to use stosq/stosb, movsq/movsb, cmpsq/cmpsb sequences
which are well optimized on AMD and Intel. Do not just use the '*b'
string
kernel - Refactor bcmp, bcopy, bzero, memset
* For now continue to use stosq/stosb, movsq/movsb, cmpsq/cmpsb sequences
which are well optimized on AMD and Intel. Do not just use the '*b'
string op. While this is optimized on Intel it is not optimized on
AMD.
* Note that two string ops in a row result in a serious pessimization.
To fix this, for now, conditionalize the movsb, stosb, or cmpsb op so
it is only executed when the remaining count is non-zero. That is,
assume nominal 8-byte alignment.
* Refactor pagezero() to use a movq/addq/jne sequence. This is
significantly faster than movsq on AMD and only just very slightly
slower than movsq on Intel.
* Also use the above adjusted kernel code in libc for these functions,
with minor modifications. Since we are copying the code wholesale,
replace the copyright for the related files in libc.
* Refactor libc's memset() to replicate the data to all 64 bits code and
then use code similar to bzero().
Reported-by: mjg_ (info on pessimizations)
show more ...
|
|
Revision tags: v5.2.0, v5.3.0, v5.2.0rc, v5.0.2, v5.0.1, v5.0.0, v5.0.0rc2, v5.1.0, v5.0.0rc1, v4.8.1, v4.8.0, v4.6.2, v4.9.0, v4.8.0rc, v4.6.1, v4.6.0, v4.6.0rc2, v4.6.0rc, v4.7.0, v4.4.3, v4.4.2, v4.4.1, v4.4.0, v4.5.0, v4.4.0rc |
|
| #
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 ...
|
|
Revision tags: v4.2.4, v4.3.1, v4.2.3, v4.2.1, v4.2.0, v4.0.6, v4.3.0, v4.2.0rc, v4.0.5, v4.0.4, v4.0.3, v4.0.2, v4.0.1, v4.0.0, v4.0.0rc3, v4.0.0rc2, v4.0.0rc, v4.1.0, v3.8.2, v3.8.1, v3.6.3, v3.8.0, v3.8.0rc2, v3.9.0, v3.8.0rc, v3.6.2, v3.6.1, v3.6.0, v3.7.1, v3.6.0rc, v3.7.0, v3.4.3, v3.4.2, v3.4.0, v3.4.1, v3.4.0rc, v3.5.0, v3.2.2, v3.2.1, v3.2.0, v3.3.0, v3.0.3, v3.0.2, v3.0.1, v3.1.0, v3.0.0 |
|
| #
86d7f5d3 |
| 26-Nov-2011 |
John Marino <draco@marino.st> |
Initial import of binutils 2.22 on the new vendor branch
Future versions of binutils will also reside on this branch rather
than continuing to create new binutils branches for each new version.
|
|
Revision tags: v2.12.0, v2.13.0, v2.10.1, v2.11.0, v2.10.0, v2.9.1, v2.8.2, v2.8.1, v2.8.0, v2.9.0, v2.6.3, v2.7.3, v2.6.2, v2.7.2, v2.7.1, v2.6.1, v2.7.0, v2.6.0 |
|
| #
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 ...
|
| #
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 ...
|