#
285830 |
|
23-Jul-2015 |
gjb |
- Copy stable/10@285827 to releng/10.2 in preparation for 10.2-RC1 builds. - Update newvers.sh to reflect RC1. - Update __FreeBSD_version to reflect 10.2. - Update default pkg(8) configuration to use the quarterly branch.[1]
Discussed with: re, portmgr [1] Approved by: re (implicit) Sponsored by: The FreeBSD Foundation |
#
269101 |
|
25-Jul-2014 |
ian |
MFC r261530
Set the malloc alignment to 64 bytes on platforms that use the U-Boot API device drivers. Recent versions of u-boot run with the MMU enabled, and require DMA-based I/O to be aligned to cache line boundaries.
|
#
256281 |
|
10-Oct-2013 |
gjb |
Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation
|
#
136093 |
|
03-Oct-2004 |
stefanf |
Don't add integers to void pointers.
|
#
84221 |
|
30-Sep-2001 |
dillon |
Add __FBSDID()s to libstand
|
#
60481 |
|
12-May-2000 |
peter |
Fix the real problem that broke the Alpha loader this last week. It was not the fault of the module code, nor FICL. The malloc code requires sbrk() to return addresses that were at least 16 byte aligned. If the Alpha loader happened to be 8 byte but not 16 byte aligned in length, then you would get a zfree() panic at startup.
Incidently, this affected the i386 loader as well, and explains why the static heap changed things and why jlemon had trouble when the bss was not ending at a multiple of 8 bytes.
My fix is to 16 byte align it on all arches, even though the x86 version only required 8 byte alignment (struct MemNode is smaller there). We could page align it if we wanted to be paranoid, but it isn't presently necessary.
|
#
50476 |
|
28-Aug-1999 |
peter |
$Id$ -> $FreeBSD$
|
#
39665 |
|
26-Sep-1998 |
msmith |
Replace the old and extremely icky Mach/NetBSD allocator with a similarly compact and much better one donated by Matt Dillon. Implement a simple sbrk() which uses the existing setheap() api.
Remove the custom allocator from the UFS code. It wasn't working quite right, and it shouldn't be needed with the new allocator.
Fix a serious problem with changing the value of already-existent environment variables. Don't attempt to modify the supposedly-const argument to putenv()
Fix an off-by-one sizing error in the zipfs code detected by the new allocator.
Submitted by: zmalloc from Matt Dillon <dillon@backplane.com>
|