| Age | Commit message (Collapse) | Author |
|---|
|
protocol specific code. No behaviour change
|
|
until they're zombies and then send them signals (for intr mounts). Until
that is untangled, the sigacts change is unsafe. sthen@ was the victim
for this one
|
|
therefore affected by the same bugs I've fixed a week ago.
The high part was being clipped for all exponents greater or equal
to 52. Fix this to use RESTYPE_BITS instead; also make the code
consistent.
|
|
|
|
|
|
Therefore, in nextafter() and nextafterf():
- if(x==y) return x; /* x=y, return x */
- if(x==y) return y; /* x=y, return y */
This matters for negative zero inputs of x or y.
|
|
Besides being wrong, they are part of sndio internals and don't need
to be exposed in such a high level man page.
|
|
macros instead of hardcoded strings. No object change
|
|
need to query the server for supported parameters. So stop using the
AMSG_GETCAP message, and remove it completely from the aucat protocol.
|
|
with the server. As we're at it use the same protocol for midi and
audio. Now, both audio and midi code use the same SNDIO_DEBUG environment
variable to turn on/off DPRINTF's.
|
|
HPPA longjmp tests that the env parameter < the current stack pointer.
The test relies on the stack being at the end of the memory space.
This test is wrong for a couple of reasons:
- the main stack is at 0x78000000-0x80000000, but allocations between
0x80000000-0xc0000000 are available to the program,
- pthread stacks may be at any place in the address space, allowing a
heap-allocated env parameter to fail the check.
ok deraadt@, kettenis@, guenther@ at least
|
|
to handle that with the sigacts change.
problem observed and diagnosed by claudio@ and kettenis@
|
|
Diff from Alexander Polakov.
OK phessler@
|
|
be shared (p_sigignore, p_sigcatch, P_NOCLDSTOP, P_NOCLDWAIT) moves
to struct sigacts, wihle stuff that should be per rthread (ps_oldmask,
SAS_OLDMASK, ps_sigstk) moves to struct proc. Treat the coredumping
state bits (ps_sig, ps_code, ps_type, ps_sigval) as per-rthread
until our locking around coredumping is better.
Oh, and remove the old SunOS-compat ps_usertramp member.
"I like the sound of this" tedu@
|
|
Additional testing by jasper@ and pea@
|
|
them in files named mio_<backend>.c
No behaviour change.
|
|
|
|
bits, because "behavior is implementation defined in this case".
However, this is wrong; behavior is undefined if the right operand
is greater than or equal to the width of the promoted left operand.
This broke {,l}lrint{,f} (64-bit architectures), and llrint{,f}
(32-bit architectures) where results are actually 64-bit values.
The high part was clipped for all exponents greater or equal to 52.
Fix this to use RESTYPE_BITS instead; {,l}lrint{,f} are now able
to pass our regression tests, and I think are right now.
|
|
|
|
|
|
|
|
we round towards -inf or +inf.
|
|
and the problem isn't obvious yet.
|
|
ok miod
|
|
|
|
|
|
audio-related functions and put them in files named sio_<backend>.c
No behaviour changes.
|
|
for chars.
|
|
Add pcb_fsbase to the PCB for tracking what the value for the thread
is, and ci_cur_fsbase to struct cpu_info for tracking the CPU's current
value for FS.base, then on return to user-space, skip the setting if the
CPU has the right value already. Non-threaded processes without TLS leave
FS.base zero, which can be conveniently optimized: setting %fs zeros
FS.base for fewer cycles than wrmsr.
ok kettenis@
|
|
tested by otto@; ok miod@
|
|
about cert checking in OpenSSH. Man page wording tweaks thanks to
jmc@.
ok henning@, jmc@; positive feedback from djm@, ajacoutat@
Committing now to reuse guenther@'s libc minor bump instead of
cranking it again, as suggested by deraadt@.
|
|
ok nicm
|
|
to return -1 in case of an unprintable character.
ok nicm jmc
|
|
On mips64, also correct the name called from plain cerror to __cerror.
"looks correct" miod@
|
|
Single byte sequences other than ASCII are not valid UTF-8, so they should
test false in single-byte ctype functions like isprint().
Remove some dead #ifdef'd code while here.
ok phessler nicm mikeb
|
|
|
|
stack.
ok fgsch@
|
|
stack.
ok deraadt@, fgsch@
|
|
ok claudio@ jsing@
|
|
"if you have checked this I am ok with it" does not mean
1) not to pay attention to breaking news after I tell you that and
2) not to get ok's from the others this had been shown to.
I am absolutely not ok with thig going in with only *my* ok. There's a reason why we want more than one ok on important commits
ok deraadt@ for the backout
|
|
DigiCert High Assurance CA-3
Go Daddy Secure Certification Authority
COMODO High-Assurance Secure Server CA
Equifax Secure Certificate Authority
VeriSign Class 3 Public Primary Certification Authority - G5
Entrust Certification Authority - L1C
Entrust.net Secure Server Certification Authority
cross checked with mozilla
ok beck@
|
|
Fixes build on NFS src with no root access. ok jasper@
|
|
|
|
out by Andres Perera (andres.p at zoho.com)
|
|
abused to cause an integer overflow and serves no real purpose.
Found by Alexander Schrijver.
ok millert deraadt
|
|
discussed with millert and guenther
ok guenther
|
|
as requested and give a correct estimate when they don't all fit,
and in unvis() decode them instead of erroring
ok nicm@, deraadt@
|
|
various zero-width characters (e.g. diacritical marks). Also fix runetype
mask definitions so that mklocale interprets zero width properly.
Diff from Alexander Polakov.
Character definition changes checked against Unicode 5.2 by me.
ok matthew nicm
|
|
local registers for a few temporaries. This was changed to use two global
registers. Maybe to permit use in-kernel without conflicting with the
register V7 register window handlers. (Was this done by Chris Torek? Is this
related to Gordon Irlam's work? Or was it in NetBSD? Hard to tell because
NetBSD removed their original cvs tree.)
In V8 the ABI was tightened; more global registers became offlimits in
different ways. We started supporting sun4m, and did not consider this.
As a result, the global registers chosen are the wrong choice. In
particular, %g7 is a poor choice for upcoming TLS work. It looks like
it is safer to use %g5 and %g6 since these functions are "system software".
All re-entrant parts of the system save it.
On sparc64 these functions are in libc per ABI requirement, but are unused.
On sparc, they occur in bootblocks (no reentrancy), kernel (reentrancy saves
globals; kernel is not ABI compliant), userland libc (signal handlers save
globals), and ld.so (symbol binding is not re-entrant on its own).
Discussed rather extensively with guenther, kettenis, miod and drahn.
|
|
|
