| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Reference-count the directory data so that
we don't leak memory.
* Correctly step through the directory records
(skipping unrecognized extensions)
* Use better defaults for file modes
* Sort directory entries by offset of the end of the file
rather than the beginning of the file. This fixes a
lot of "out-of-order" problems with zero-length files,
in particular.
* Style fixes, remove some debug code, add some error messages.
|
|
|
|
| |
In particular, bsdtar should now recognize ISO9660 images.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This seems to be able to extract a TOC and extract files from
the couple of ISO images I've tested it with.
Treat this as experimental proof-of-concept code for the
moment. There are still a bunch of debug messages (there
are a few oddities in ISO9660 that I haven't yet figured
out how to handle), a lot of bugs to be addressed (this
code leaks memory very badly), and a lot of missing features (no
Rockridge support, in particular). I'd appreciate
feedback from anyone who understands ISO9660 format
better than I do. ;-)
Suggested by: Robert Watson
|
|
|
|
|
|
|
| |
PR: bin/72394
Submitted by: Dan Nelson
Reviewed by: deischen
MFC after: 2 weeks
|
|
|
|
|
| |
PR: bin/75656
MFC after: 2 weeks
|
|
|
|
|
|
| |
Submitted by: Kurt Jaeger <pi at complx dot LF dot net>
Approved by: ru
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
| |
the regular ustar entry. The old code sometimes created
a too-long name that overflowed the ustar fields and triggered
an internal assertion failure. This version should be more
robust.
Thanks to: Michal Listos
Fixes: bin/74385
MFC after: 15 days
|
|
|
|
|
| |
o Sticky bit is actually defined as S_ISTXT not S_ISVTX.
o Sticky bit is wrapped in if __BSD_VISIBLE not _POSIX_SOURCE.
|
|
|
|
|
| |
PR: docs/75615
Submitted by: n-kogane@syd.odn.ne.jp
|