| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
puts it before library's object files, making the whole constuct useless.
|
| |
|
|
|
|
|
|
|
|
|
| |
scheme allowed for 1024 PTE pages, each containing 256 PTEs.
This yielded 2GB of KVA. This is not enough to boot a kernel
on a 16GB box and in general too low for a 64-bit machine.
By adding a level of indirection we now have 1024 2nd-level
directory pages, each capable of supporting 2GB of KVA. This
brings the grand total to 2TB of KVA.
|
|
|
|
|
| |
Found by: Coverity Prevent
Coverity ID: CID 3132
|
|
|
|
| |
libraries might depend on versioned symbols from libc.
|
|
|
|
| |
architectures. Linker defines end is synonym for _end.
|
|
|
|
| |
as static later.
|
| |
|
|
|
|
|
| |
SSP functions into FreeBSD libc. Use the same file name and location
for consistency with other projects.
|
|
|
|
| |
Suggested by: deischen
|
|
|
|
|
|
|
| |
that would cause the selected shared threading library to be
overwritten with its 32-bit version on amd64.
PR: amd64/112509
|
|
|
|
| |
export them.
|
|
|
|
| |
Submitted by: ru
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
| |
can be used on any read socketopt).
-Clean up of sendmsg call and make it conformant when no syscall
is available.
|
|
|
|
|
| |
PR: 112704
Submitted by: kou@cozmixng.org
|
|
|
|
|
| |
world and it wreak havoc if libc collides with other versioned
libraries.
|
|
|
|
|
|
| |
descriptor number.
Approved by: glebius (mentor)
|
|
|
|
|
|
| |
PR: docs/78915
Submitted by: Marc Olzheim <marcolz@stack.nl>
MFC after: 1 week
|
|
|
|
| |
Submitted by: marius
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
RIPEMD160_Update were broken when all of the following conditions
applied:
(1) The platform is i386.
(2) The program calling *_Update is statically linked to libmd.
(3) The buffer provided to *_Update is aligned modulo 4 bytes.
(4) The buffer extends beyond 2GB.
Due to the design of this code, SHA1_Update and RIPEMD160_Update will
still be broken if conditions (1)-(3) apply AND the buffer extends
beyond 4GB (i.e., there is an integer overflow in computing "data + len").
Since this remaining bug simply replaces SIGSEGV with a bogus hash (and
non-broken programs should never provide such operands) I don't consider
it to be a serious problem.
MFC After: 1 week
PR: kern/102795
|
|
|
|
| |
Pointed out by: deischen
|
|
|
|
|
|
|
| |
arch. It can be named differently depending on the arch (.mcount,
_mcount).
Submitted by: marius
|
|
|
|
|
|
|
|
|
|
| |
Warning, after symbol versioning is enabled, going back is not easy
(use WITHOUT_SYMVER at your own risk).
Change the default thread library to libthr.
There most likely still needs to be a version bump for at least the
thread libraries. If necessary, this will happen later.
|
|
|
|
|
|
| |
passed storage buffers rather than using static storage. Reimplement
ether_ntoa() and ether_aton() in terms of these functions. These variants
are thread-safe.
|
| |
|
|
|
|
| |
- Replace magic 14 with PIL_TICK.
|
|
|
|
|
|
|
| |
is not performance critical code anyway. Also, avoid using strlen() to
obtain information which we already have.
MFC after: 3 weeks
|
|
|
|
| |
Submitted by: Bård Skaflestad <bardsk@math.ntnu.no>
|
|
|
|
| |
that I make stupid fundamental mistakes like this when I don't.
|
| |
|
|
|
|
| |
MFC after: 3 weeks
|
|
|
|
| |
MFC after: 3 weeks
|
|
|
|
|
|
| |
flopen(3) function which reliably opens and locks a file.
MFC after: 3 weeks
|
|
|
|
|
|
|
| |
and its bibliography.
Submitted by: Tomoyuki Okazaki <okazaki at kick dot gr dot jp>
MFC after: 1 month
|
| |
|
|
|
|
|
|
| |
PR: kern/112515
Submitted by: Ryan C. Gordon <icculus@icculus.org>
MFC after: 3 weeks
|
|
|
|
| |
even if the programmer asks for zero padding.
|
|
|
|
| |
Reported by: Bruno Haible
|
| |
|
|
|
|
|
|
| |
with GEOM providers.
OK'ed by: phk
|
|
|
|
|
| |
Approved by: keramida (mentor)
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
that ints have >= 31 value bits elsewhere. s/int/int32_t/ seems to
have been done too globally for all other files in msun/src before
msun/ was imported into FreeBSD.
Minor fixes in comments.
e_lgamma_r.c:
Describe special cases in more detail:
- exception for lgamma(0) and lgamma(neg.integer)
- lgamma(-Inf) = Inf. This is wrong but is required by C99 Annex F. I
hope to change this.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(1) tgamma(-Inf) returned +Inf and failed to raise any exception, but
should always have raised an exception, and should behave like
tgamma(negative integer).
(2) tgamma(negative integer) returned +Inf and raised divide-by-zero,
but should return NaN and raise "invalid" on any IEEEish system.
(3) About half of the 2**52 negative intgers between -2**53 and -2**52
were misclassified as non-integers by using floor(x + 0.5) to round
to nearest, so tgamma(x) was wrong (+-0 instead of +Inf and now NaN)
on these args. The floor() expression is hard to use since rounding
of (x + 0.5) may give x or x + 1, depending on |x| and the current
rounding mode. The fixed version uses ceil(x) to classify x before
operating on x and ends up being more efficient since ceil(x) is
needed anyway.
(4) On at least the problematic args in (3), tgamma() raised a spurious
inexact.
(5) tgamma(large positive) raised divide-by-zero but should raise overflow.
(6) tgamma(+Inf) raised divide-by-zero but should not raise any exception.
(7) Raise inexact for tiny |x| in a way that has some chance of not being
optimized away.
The fix for (5) and (6), and probably for (2), also prevents -O optimizing
away the exception.
PR: 112180 (2)
Standards: Annex F in C99 (IEC 60559 binding) requires (1), (2) and (6).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
values in more detail, and change the style of this comment to be closer
to fdlibm and C99:
- tgamma(-Inf) was undocumented and is wrong (+Inf, should be NaN)
- tgamma(negative integer) is as intended (+Inf) but not best for IEEE-754
(NaN)
- tgamma(-0) was documented as being wrong (+Inf) but was correct (-Inf)
- documentation of setting of exceptions (overflow, etc.) was more
complete here than in most of libm, but was further from matching
the actual setting than in most of libm, due to various bugs here
(primarily, always evaluating +Inf one/zero and getting unwanted
divide-by-zero exceptions from this). Now the actual behaviour with
gcc -O0 is documented. Optimization still breaks setting of exceptions
all over libm, so nothing can depend on this working.
- tgamma(NaN)'s exception was documented as being wrong (invalid) but was
correct (no exception with IEEEish NaNs).
Finish (?) rev.1.5. gamma was not renamed to tgamma in one place.
Finish (?) rev.1.6. errno.h was not completely removed.
|
|
|
|
|
|
|
| |
This is a no-op as far as FreeBSD is concerned, but makes libarchive
more autoconf-friendly.
Approved by: kientzle
|
|
|
|
| |
Tested with: md5(1)
|
| |
|
|
|
|
|
|
|
|
|
| |
Not because I admit they are technically wrong and not because of bug
reports (I receive nothing). But because I surprisingly meets so
strong opposition and resistance so lost any desire to continue that.
Anyone who interested in POSIX can dig out what changes and how
through cvs diffs.
|