src/lib/libc/amd64/sys, branch release/6.0.0_cvs

This commit was manufactured by cvs2svn to create tag

2005-11-03T00:35:26+00:00

'RELENG_6_0_0_RELEASE'.

This commit was manufactured to restore the state of the 6.0-RELEASE image.

Do not try to store 64 bits into 32 bit errno variable. With the changed libc

2005-04-21T12:47:08+00:00

data layout, this was corrupting _PathLocale variable leading to programs
dumping core in non-default locales.

Fix brk(3). The stack was unbalanced when we jumped to cerror. Oops!

2004-10-27T17:11:43+00:00

This causes nasty things like SEGV or a cpu spin when we return.

Submitted by: "James R. Van Artsalen"

Change the syscall stub branch orders so that the static branch prediction

2004-02-22T02:11:39+00:00

will assume that syscalls will succeed rather than fail.

Provide sysarch(2) prototypes in the MD sysarch.h headers. While I'm

2004-01-09T16:52:09+00:00

at it, use the ANSI C generic pointer type for the second argument,
thus matching the documentation.

Remove the now extraneous (and now conflicting) function declarations
in various libc sources.  Remove now unnecessary casts.

Reviewed by:	bde

Add implementations of amd64_[gs]et_[fg]sbase().

2003-10-23T06:07:09+00:00

Sigh. I can't win anything. Use addq rather than addl with %rsp.

2003-09-04T00:31:45+00:00

Apply same basic fix for getcontext(2) as for i386. Store the return

2003-09-04T00:29:12+00:00

value for getcontext() in a preserved register rather than on the stack.
The second time around, the stack value would likely have changed so we
can't depend on it for the return value.

Fix some minor whitespace botches

2003-09-04T00:26:40+00:00

Add the mlockall() and munlockall() system calls.

2003-08-11T07:14:08+00:00

 - All those diffs to syscalls.master for each architecture *are*
   necessary. This needed clarification; the stub code generation for
   mlockall() was disabled, which would prevent applications from
   linking to this API (suggested by mux)
 - Giant has been quoshed. It is no longer held by the code, as
   the required locking has been pushed down within vm_map.c.
 - Callers must specify VM_MAP_WIRE_HOLESOK or VM_MAP_WIRE_NOHOLES
   to express their intention explicitly.
 - Inspected at the vmstat, top and vm pager sysctl stats level.
   Paging-in activity is occurring correctly, using a test harness.
 - The RES size for a process may appear to be greater than its SIZE.
   This is believed to be due to mappings of the same shared library
   page being wired twice. Further exploration is needed.
 - Believed to back out of allocations and locks correctly
   (tested with WITNESS, MUTEX_PROFILING, INVARIANTS and DIAGNOSTIC).

PR:             kern/43426, standards/54223
Reviewed by:    jake, alc
Approved by:    jake (mentor)
MFC after:	2 weeks