| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
strerror_r(). Doing this allows us to ensure that strerror_r() always
fills the supplied buffer regardless of EINVAL or ERANGE errors.
strerror()'s semantics have changed slightly such that an argument of
0 is now considered invalid and errno is set to EINVAL.
Remove internal regression test for strerror() and strerror_r(). This
will be reincarnated in src/tools/regression/lib/libc/string.
In strerror(3), add a comment about strerror()'s bogus return type.
PR: 44356
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Stop calling system calls "function calls".
Use "The .Fn system call" a-la "The .Nm utility".
When referring to a non-BSD implementation in
the HISTORY section, call syscall a function,
to be safe.
|
|
|
|
|
|
|
|
| |
conversion specifications to completely specify the resulting struct tm.
PR: 46331
Submitted by: Christian S.J. Peron
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
| |
from "unix" back to "local". Add some compat stuff so both
ways work for some time.
Reviewed by: phk
Approved by: imp (UPDATING)
Requested by: iedowse, lukem@netbsd.org
|
|
|
|
|
|
|
|
| |
does not hurt anything because uipc_ctloutput() does not check
sopt->sopt_level.
Pointed out by: ru
MFC after: 1 week
|
|
|
|
|
|
|
| |
This should be considered highly experimental for the moment.
Submitted by: David Schultz <dschultz@uclink.Berkeley.EDU>
MFC after: 3 weeks
|
|
|
|
|
|
|
|
|
| |
The bug does not affect anything because SOCK_STREAM == LOCAL_PEERCRED == 0x1.
PR: bin/46165
Submitted by: Alain Thivillon <at@rominet.net>
Reviewed by: dd
MFC after: 1 week
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Submitted by: R. Imura <imura@ryu16.org>
Approved by: re (murray)
|
|
|
|
| |
Approved by: re
|
|
|
|
|
|
|
| |
necessary nowadays, but is documented as "required", and may
become so again in the future.
Approved by: re
|
|
|
|
|
|
| |
PR: docs/46183
Submitted by: Dirk Gouders <gouders@et.bocholt.fh-ge.de>
Approved by: re
|
|
|
|
| |
Approved by: re
|
|
|
|
| |
Approved by: re
|
|
|
|
| |
Approved by: re
|
|
|
|
| |
Approved by: re
|
|
|
|
| |
Approved by: re
|
|
|
|
|
|
| |
localtime/mktime/tmcomp and friends on ia64.
Approved by: re
|
|
|
|
| |
Approved by: re
|
|
|
|
|
|
|
| |
are marked up in stdio(3), and because they are defined expressions
of type "FILE *".
Approved by: re
|
|
|
|
| |
Approved by: re
|
|
|
|
| |
Approved by: re
|
|
|
|
| |
Approved by: re
|
|
|
|
|
|
| |
Reviewed by: benno
Approved by: re (blanket)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
when trying to store the year in a signed int. The maximum time_t on ia64
is around 292 billion years in the future, but 'int' and struct tm.tm_year
can only represent then ext 2.1 billion years or so.
This solves the problem of mktime/localtime looping on ia64. Unfortunately,
the standards say that tm_year is an 'int', so we are still stuck with a
y2147483647 bug. bash2's configure script looks for bugs in mktime() and
fails on ia64 because of this. However, mktime() on FreeBSD fails the test
normally anyway so this is no big loss.
This change does not affect any other platforms besides ia64.
Approved by: re
|
| |
|
| |
|
|
|
|
| |
Approved by: re
|
|
|
|
|
| |
Submitted by: jlemon
Approved by: re
|
|
|
|
| |
Approved by: re
|
| |
|
|
|
|
| |
future ahead of it.
|
|
|
|
|
|
|
|
|
|
| |
been repo-copied from src/lib/libc/uuid to src/include. Update the
makefiles.
While in src/include/Makefile, reformat and resort INCS. Reverting
the functional change only involves removing uuid.h.
Pompted by: ru
|
|
|
|
|
|
| |
section.
PR: 43270
|
|
|
|
|
|
| |
I've no idea if this is the right behavior for the library, but this
at least fixes the build, and matches what seems to be alfred's intent
in the commit message for 1.19.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
sysconf.c:
Use 'break' rather than 'goto yesno' in sysconf.c so that we report a '0'
return value from the kernel sysctl.
vfs_aio.c:
Make aio reset its configuration parameters to -1 after unloading
instead of 0.
posix4_mib.c:
Initialize the aio configuration parameters to -1
to indicate that it is not loaded.
Add a facility (p31b_iscfg()) to determine if a posix4 facility has been
initialized to avoid having to re-order the SYSINITs.
Use p31b_iscfg() to determine if aio has had a chance to run yet which
is likely if it is compiled into the kernel and avoid spamming its
values.
Introduce a macro P31B_VALID() instead of doing the same comparison over
and over.
posix4.h:
Prototype p31b_iscfg().
|
|
|
|
|
|
|
|
|
| |
libc. I want to keep these in some version for the thread
library/ies, but don't know whether to have them repo-copied
to libc_r or renamed and kept in libc.
Change the name of an alpha macro that was changed with the
system call commit.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
subsystems capabilities:
_SC_AIO_LISTIO_MAX returns the default of _POSIX_AIO_LISTIO_MAX
_SC_AIO_MAX returns the default _POSIX_AIO_MAX
_SC_AIO_PRIO_DELTA_MAX returns the default of 0
Without these adjustments the values returned are -1 even when the
aio side of the kernel returns '0' for them which is incorrect.
Noticed by: Craig Rodrigues <rodrigc@attbi.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
architecture, mainly to avoid getting a SIGFPE signal sent
when calling strtod(3) with certain input.
The SIGFPE has been sent because the code was not aware that
a Gradual Underflow is handled in software via traps on the
Alpha architecture, but is not implemented in our Alpha kernel
layer.
With `Sudden_Underflow' defined, strtod(3) should not depend
on Gradual Underflow and adjust its calculations accordingly,
which means that other, more subtle errors than the sending of
SIGFPE could be solved by this.
Discussed with: bde
PR: alpha/12623
PR: alpha/17032
PR: alpha/43567
MFC after: 7 days
|
|
|
|
|
|
|
| |
that we not use it here. In its place I've put a comment about the
current state of play.
Submitted by: bde
|