about summary refs log tree commit diff
path: root/src/liblibc
AgeCommit message (Collapse)AuthorLines
2018-03-26Update liblibc submodule to the 0.2.40 releaseFrancis Gagné-0/+0
2018-03-12Update libc to 0.2.39Bryan Drewery-0/+0
CC #42681
2018-01-24Update libcMarco A L Barbosa-0/+0
2018-01-08Upgrade liblibc to latest upstream version.Ed Schouten-0/+0
This version of liblibc is a prerequisite for getting libstd to build on CloudABI.
2017-12-17add aarch64-unknown-openbsd supportSébastien Marie-0/+0
- make liblibc to point to libc with aarch64-unknown-openbsd - make c_char (in std::os::raw) to point to right value
2017-11-26Update libc to include latest Fuchsia fixTaylor Cramer-0/+0
2017-11-16Update libc to include Fuchsia changesTaylor Cramer-0/+0
2017-11-14Update libc (new const definitions for Linux sparc64)Marco A L Barbosa-0/+0
2017-11-09Use getrandom syscall for all Linux and Android targets.Marco A L Barbosa-0/+0
2017-10-31Bump libc to 0.2.33Marco A L Barbosa-0/+0
2017-10-19Update libc to include linux gnux32 fixesMarco A L Barbosa-0/+0
2017-09-24bump liblibc to 0.2.31James Tucker-0/+0
2017-09-21Trim and document libc shimTamir Duberstein-0/+0
2017-09-08Update liblibc submodule to include latest uclibc changesTobias Schaffner-0/+0
2017-08-30Update libc to fix sparc compilesAlex Crichton-0/+0
2017-08-28Update the libc submoduleAlex Crichton-0/+0
Brings in a few fixes for wasm/asmjs
2017-08-07addrinfo hint in lookup_host() needs clean initialization on all platformsDanek Duvall-0/+0
Fixes #43649
2017-07-18Update liblibcJeremy Soller-0/+0
2017-06-20Update libc to 0.2.24Malo Jaffré-0/+0
Fixes #42427.
2017-05-04Reload nameserver information on lookup failureJon Gjengset-0/+0
As discussed in #41570, UNIX systems often cache the contents of /etc/resolv.conf, which can cause lookup failures to persist even after a network connection becomes available. This patch modifies lookup_host to force a reload of the nameserver entries following a lookup failure. This is in line with what many C programs already do (see #41570 for details). On systems with nscd, this should not be necessary, but not all systems run nscd. Introduces an std linkage dependency on libresolv on macOS/iOS (which also makes it necessary to update run-make/tools.mk). Fixes #41570. Depends on rust-lang/libc#585.
2017-04-20Update libc to include x86_64-linux-android supportMarco A L Barbosa-0/+0
2017-03-25Update libc to 0.2.21Marco A L Barbosa-0/+0
2017-02-22Update name_bytes, scoop up latest libcRaph Levien-0/+0
Update the implementation of name_bytes to use the owned string (which is thread safe). Also bump the src/liblibc submodule now that's merged.
2017-02-06liblibc: Update to include aarch64-unknown-freebsd supportJean-Sébastien Pédron-0/+0
2017-02-04libstd/net: Add `peek` APIs to UdpSocket and TcpStreamTyler Julian-0/+0
These methods enable socket reads without side-effects. That is, repeated calls to peek() return identical data. This is accomplished by providing the POSIX flag MSG_PEEK to the underlying socket read operations. This also moves the current implementation of recv_from out of the platform-independent sys_common and into respective sys/windows and sys/unix implementations. This allows for more platform-dependent implementations.
2017-01-03Properly ban the negation of unsigned integers in type-checking.Eduard-Mihai Burtescu-0/+0
2016-12-30sparc64-linux supportJorge Aparicio-0/+0
2016-12-21Update liblibc, go back to lazy linking openlibmJeremy Soller-0/+0
2016-12-03update src/liblibc to include i686-unknown-openbsd libc definitionSébastien Marie-0/+0
2016-11-16rustc: Implement #[link(cfg(..))] and crt-staticAlex Crichton-0/+0
This commit is an implementation of [RFC 1721] which adds a new target feature to the compiler, `crt-static`, which can be used to select how the C runtime for a target is linked. Most targets dynamically linke the C runtime by default with the notable exception of some of the musl targets. [RFC 1721]: https://github.com/rust-lang/rfcs/blob/master/text/1721-crt-static.md This commit first adds the new target-feature, `crt-static`. If enabled, then the `cfg(target_feature = "crt-static")` will be available. Targets like musl will have this enabled by default. This feature can be controlled through the standard target-feature interface, `-C target-feature=+crt-static` or `-C target-feature=-crt-static`. Next this adds an gated and unstable `#[link(cfg(..))]` feature to enable the `crt-static` semantics we want with libc. The exact behavior of this attribute is a little squishy, but it's intended to be a forever-unstable implementation detail of the liblibc crate. Specifically the `#[link(cfg(..))]` annotation means that the `#[link]` directive is only active in a compilation unit if that `cfg` value is satisfied. For example when compiling an rlib, these directives are just encoded and ignored for dylibs, and all staticlibs are continued to be put into the rlib as usual. When placing that rlib into a staticlib, executable, or dylib, however, the `cfg` is evaluated *as if it were defined in the final artifact* and the library is decided to be linked or not. Essentially, what'll happen is: * On MSVC with `-C target-feature=-crt-static`, the `msvcrt.lib` library will be linked to. * On MSVC with `-C target-feature=+crt-static`, the `libcmt.lib` library will be linked to. * On musl with `-C target-feature=-crt-static`, the object files in liblibc.rlib are removed and `-lc` is passed instead. * On musl with `-C target-feature=+crt-static`, the object files in liblibc.rlib are used and `-lc` is not passed. This commit does **not** include an update to the liblibc module to implement these changes. I plan to do that just after the 1.14.0 beta release is cut to ensure we get ample time to test this feature. cc #37406
2016-10-24Support for aarch64 architecture on FuchsiaRaph Levien-0/+0
This patch adds support for the aarch64-unknown-fuchsia target. Also updates src/liblibc submodule to include required libc change.
2016-10-22Update libc submodule with corresponding fuchsia changesRaph Levien-0/+0
Also trim os::fuchsia::raw architectures.
2016-10-11std: Update liblibc submoduleAlex Crichton-0/+0
This fixes compilation on the s390x target
2016-10-09use MSG_NOSIGNAL on all relevant platformsMathieu Poumeyrol-0/+0
2016-09-28use MSG_NOSIGNAL from liblibcMathieu Poumeyrol-0/+0
2016-09-26When getaddrinfo returns EAI_SYSTEM retrieve actual error from errno.Tomasz Miąsko-0/+0
Fixes issue #36546. This change also updates libc to earliest version that includes EAI_SYSTEM constant.
2016-09-09Add s390x supportUlrich Weigand-0/+0
This adds support for building the Rust compiler and standard library for s390x-linux, allowing a full cross-bootstrap sequence to complete. This includes: - Makefile/configure changes to allow native s390x builds - Full Rust compiler support for the s390x C ABI (only the non-vector ABI is supported at this point) - Port of the standard library to s390x - Update the liblibc submodule to a version including s390x support - Testsuite fixes to allow clean "make check" on s390x Caveats: - Resets base cpu to "z10" to bring support in sync with the default behaviour of other compilers on the platforms. (Usually, upstream supports all older processors; a distribution build may then chose to require a more recent base version.) (Also, using zEC12 causes failures in the valgrind tests since valgrind doesn't fully support this CPU yet.) - z13 vector ABI is not yet supported. To ensure compatible code generation, the -vector feature is passed to LLVM. Note that this means that even when compiling for z13, no vector instructions will be used. In the future, support for the vector ABI should be added (this will require common code support for different ABIs that need different data_layout strings on the same platform). - Two test cases are (temporarily) ignored on s390x to allow passing the test suite. The underlying issues still need to be fixed: * debuginfo/simd.rs fails because of incorrect debug information. This seems to be a LLVM bug (also seen with C code). * run-pass/union/union-basic.rs simply seems to be incorrect for all big-endian platforms. Signed-off-by: Ulrich Weigand <ulrich.weigand@de.ibm.com>
2016-08-29update libc submoduleJorge Aparicio-0/+0
2016-08-27update libcJorge Aparicio-0/+0
2016-07-30point the libc submodule back to rust-lang/libcJorge Aparicio-0/+0
2016-07-30arm-musl targets now use cfg(env = "musl")Jorge Aparicio-0/+0
2016-07-11libc: fast-forward for solaris `RTLD_DEFAULT`Josh Stone-0/+0
2016-06-02Update libc to bring in pthread mutex type definitionsAmanieu d'Antras-0/+0
2016-05-17std: Update libc submoduleAlex Crichton-0/+0
Brings in a fix where `-lutil` is no longer passed for musl targets, lifting the need for a musl toolchain to be installed again. Closes #33608
2016-05-15Update libc to bring in updates for android's aarch64.Nerijus Arlauskas-0/+0
2016-04-04std: Fix linking against `signal` on AndroidAlex Crichton-0/+0
Currently the minimum supported Android version of the standard library is API level 18 (android-18). Back in those days [1] the `signal` function was just an inline wrapper around `bsd_signal`, but starting in API level android-20 the `signal` symbols was introduced [2]. Finally, in android-21 the API `bsd_signal` was removed [3]. Basically this means that if we want to be binary compatible with multiple Android releases (oldest being 18 and newest being 21) then we need to check for both symbols and not actually link against either. This was first discovered in rust-lang/libc#236 with a fix proposed in rust-lang/libc#237. I suspect that we'll want to accept rust-lang/libc#237 so Rust crates at large continue to be compatible with newer releases of Android and crates, like the standard library, that want to opt into older support can continue to do so via similar means. Closes rust-lang/libc#236 [1]: https://chromium.googlesource.com/android_tools/+/20ee6d20/ndk/platforms/android-18/arch-arm/usr/include/signal.h [2]: https://chromium.googlesource.com/android_tools/+/fbd420/ndk_experimental/platforms/android-20/arch-arm/usr/include/signal.h [3]: https://chromium.googlesource.com/android_tools/+/20ee6d/ndk/platforms/android-21/arch-arm/usr/include/signal.h
2016-03-09std: Don't spawn threads in `wait_with_output`Alex Crichton-0/+0
Semantically there's actually no reason for us to spawn threads as part of the call to `wait_with_output`, and that's generally an incredibly heavyweight operation for just reading a few bytes (especially when stderr probably rarely has bytes!). An equivalent operation in terms of what's implemented today would be to just drain both pipes of all contents and then call `wait` on the child process itself. On Unix we can implement this through some convenient use of the `select` function, whereas on Windows we can make use of overlapped I/O. Note that on Windows this requires us to use named pipes instead of anonymous pipes, but they're semantically the same under the hood.
2016-03-06update the src/liblibc submoduleJorge Aparicio-0/+0
2016-03-01Update libc crateSebastian Wicki-0/+0
2016-02-22Update libc to 16f1c19Mátyás Mustoha-0/+0
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-22 14:26:17 +0000