| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
prompted by deraadt
original issue (mandoc has no support for \*(Px) reported by Matthew Dempsky;
kristaps and ingo are looking at whether to add support for the Px or not;
|
|
Based on our vfprintf etc. implementations. Wide character parts based on
NetBSD but with lots of macros expanded. Minor bump for libc.
ok kettenis espie
|
|
not reviewed yet, but it's better to track changes in cvs
|
|
|
|
Delivering FPE with non-masked exceptions doesn't work on Alpha; I
suspect there's a bug in the kernel trap handler.
FE_INEXACT is intentionally left out of FE_ALL_EXCEPT; since the
inexact exception is not being maintained. Otherwise it will lead
to the bogus results.
|
|
Prompted by mail from Mikolaj Kucharski on tech@ and discussion with
deraadt@ and millert@.
A library installing signal handlers without being asked is seriously
wrong but it appears quite a few applications now depend on the ncurses
SIGWINCH and it looks to be safe. Safer than the other signal handlers
it installs (apparently without request... boke).
ok millert
|
|
Sticky flags are in the left half of fpsr; not the undefined bits
in the right half. OK miod@.
|
|
we don't document the i386/amd64 denormalization exception.
|
|
in the right half. OK miod@.
|
|
ok jmc@
|
|
feedback & ok guenther@, matthew@
|
|
|
|
ok kettenis@
|
|
ok kettenis@
|
|
ok kettenis@
|
|
ok kettenis@
|
|
of wide characters. This will fix a problem of uim-fep pre-edit display.
OK stsp@
|
|
|
|
volatile; a similar hack was already being used in lrintf().
This will make rint and {,l}lrint family functions actually work;
i.e. on m68k rintf(8.6F) was 8.625.
|
|
ok kettenis@
|
|
ok jmc@
|
|
Instead, just document what POSIX requires.
Reminded of the problem by joachimschipper dot nl,
Feedback from matthew@, krw@, deraadt@, and ok deraadt@.
|
|
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
|
|
|
|
|
