| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Eliminate gdtoa.mk and move its contents to ${MACHINE_ARCH}/Makefile.inc.
The purpose of having a separate file involved an abandoned scheme that
would have kept contrib/gdtoa out of the include path for the rest of libc.
|
|
|
|
|
| |
The purpose of having a separate file involved an abandoned scheme that
would have kept contrib/gdtoa out of the include path for the rest of libc.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
flags, so they are not pure. Remove the __pure2 annotation from them.
I believe that the following routines and their float and long double
counterparts are the only ones here that can be __pure2:
copysign is* fabs finite fmax fmin fpclassify ilogb nan signbit
When gcc supports FENV_ACCESS, perhaps there will be a new annotation
that allows the other functions to be considered pure when FENV_ACCESS
is off.
Discussed with: bde
|
|
|
|
| |
Pointy hat to: das
|
|
|
|
|
|
| |
errno, replacing them with a discussion of IEEE exceptions where
appropriate. Cross-reference fenv(3) whenever exceptions are
mentioned.
|
|
|
|
|
|
| |
basically support this, subject to gcc's lack of FENV_ACCESS support.
In any case, the previous setting of math_errhandling to 0 is not
allowed by POSIX.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
registers as volatile. Instructions that *wrote* to FP state were
already marked volatile, but apparently gcc has license to move
non-volatile asms past volatile asms. This broke amd64's feupdateenv
at -O2 due to a WAR conflict between fnstsw and fldenv there.
|
|
|
|
| |
Obtained from: ru
|
|
|
|
|
|
|
| |
math routines that appear to be (a) correct and (b) faster than their
MI counterparts on my Pentium 4.
Obtained from: NetBSD
|
|
|
|
|
|
| |
getnetgrent() doesn't return bogus information.
MFC after: 3 days
|
|
|
|
|
|
| |
round correctly.
Noticed by: stefanf
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
not "NULL", see ascii(7).
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Also, add some hints to help people understand which
functions are most appropriate for typical uses.
|
|
|
|
|
|
| |
PR: 28890
Submitted by: matthias.andree at web dot de
MFC after: 7 days
|
|
|
|
| |
Discussed with: bde
|
| |
|
| |
|
|
|
|
|
| |
the only way to convince gcc that they read the MXCSR. The volatile
annotation may be needed elsewhere as well.
|
| |
|
| |
|
|
|
|
| |
Noticed by: ru
|
|
|
|
| |
MFC after: 3 days
|
| |
|
|
|
|
|
|
| |
GNU) for determining whether a string is an affirmative or negative
response to a question according to the current locale. This is done
by matching the response against nl_langinfo(3) items YESEXPR and NOEXPR.
|
| |
|
|
|
|
|
|
|
| |
expand and clarify the description of the client
callback functions and how they should handle errors.
Thanks to: Antony Dovgal
|
|
|
|
|
|
| |
to archive_read_open and archive_write_open.
Thanks to: Antony Dovgal
|
|
|
|
|
|
|
| |
to archive_read_next_header so the
next error doesn't just get appended.
MFC after: 7 days
|
|
|
|
| |
Submitted by: Ken Smith <kensmith@cse.Buffalo.EDU>
|
| |
|
|
|
|
|
|
|
| |
Make sure we don't confuse the reader by claiming it is.
PR: docs/75615
Submitted by: Nobuyuki Koganemaru <n-kogane@syd.odn.ne.jp>
|
|
|
|
|
| |
Submitted by: Peter Jeremy <PeterJeremy@optushome.com.au>
MFC after: 5 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
make utilities like du(1) 64bit-clean.
When this field is used, one cannot use 'fts_number' and 'fts_pointer'
fields.
This commit doesn't break API nor ABI.
This work is part of the BigDisk project:
http://www.FreeBSD.org/projects/bigdisk/
Discussed on: arch@
MFC after: 5 days
|
|
|
|
| |
defined in libdisk.h.
|
|
|
|
|
| |
Submitted by: Markus Brueffer < markus AT brueffer DOT de >
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
which doesn't end in \n, since it may be very confusing. Also this should
increase consistency, since most other config files work just fine regardless
of the presence of traling \n in the last line.
MFC After: 2 weeks
|
|
|
|
|
|
| |
Large thanks to the easy-to-read and well-documented
sys/isofs/cd9660 source code, which provided many of the
details I needed for this exercise.
|
| |
|