- 24 2月, 2016 9 次提交
-
-
由 bors 提交于
This fixes the `aarch64-linux-android` build (#31595).
-
由 bors 提交于
None
-
由 bors 提交于
I am not entirely sure I have got everything right, but if it compiles it is ok probably... I tested it with msvc x86_64 and gnu. Somehow a lot of `EXCEPTION-*` constants are dead code when running test, no idea why. I have put `#![cfg_attr(test, allow(dead_code))]` at the top for this.
-
由 bors 提交于
r? @alexcrichton
-
由 bors 提交于
The MinGW-based Python implementations would automatically do this, but if we want to use Python from the official downloads our usage of `/` instead of `\` can wreak havoc. In a few select locations just use `os.path.normpath` do do the conversions properly for us.
-
由 Alex Crichton 提交于
The MinGW-based Python implementations would automatically do this, but if we want to use Python from the official downloads our usage of `/` instead of `\` can wreak havoc. In a few select locations just use `os.path.normpath` do do the conversions properly for us.
-
由 bors 提交于
I'm a bit iffy on the return type, but `Result` would also be a bit weird... The two error cases are `Unterminated` and `InteriorNul(usize)`. I considered `from_chars(&[c_char])` but this meshes better with `as_bytes_with_nul()` and Rust code in general. Should there also be a corresponding unsafe `from_bytes_unchecked` variant?
-
由 bors 提交于
-
由 arcnmx 提交于
-
- 23 2月, 2016 19 次提交
-
-
由 Aaron Turon 提交于
-
由 arcnmx 提交于
-
由 bors 提交于
`ReadFile` and `WriteFile` take a DWORD (u32) for the length argument which was erroneously cast from a usize causing truncation. This meant methods like `write_all` and `read_exact` would unexpectedly fail if given a buffer 4 GiB or larger. We can instead just ask for `u32::MAX` bytes if the given buffer is too big.
-
由 bors 提交于
BitVector is more space efficient.
-
由 Simonas Kazlauskas 提交于
BitVector is much more space efficient.
-
由 bors 提交于
Fixes https://github.com/rust-lang/rust/issues/29548
-
由 arcnmx 提交于
-
由 arcnmx 提交于
-
由 bors 提交于
The `vfp2` option was a leftover from `armv6` compatibility features of the original armhf target. Gcc defaults to `vfp3`on `armv7` hard-float linux systems so we should make it the default for rustc too.
-
由 Corey Farwell 提交于
-
由 Oliver Middleton 提交于
`ReadFile` and `WriteFile` take a DWORD (u32) for the length argument which was erroneously cast from a usize causing truncation. This meant methods like `write_all` and `read_exact` would unexpectedly fail if given a buffer 4 GiB or larger. We can instead just ask for `u32::MAX` bytes if the given buffer is too big.
-
由 Vadim Petrochenkov 提交于
-
由 bors 提交于
This allows to search for crates in documentation and simplifies the json serialization of the search-index. fixes #14077
-
由 bors 提交于
-
由 bors 提交于
This is an implementation of rust-lang/rfcs#1443.
-
由 mitaa 提交于
-
由 Amanieu d'Antras 提交于
-
由 Vadim Petrochenkov 提交于
-
由 bors 提交于
Hello. I came across some minor spelling mistakes while going through the documentation for the `Iterator` trait. Also includes a suggested styling fix. r? @steveklabnik
-
- 22 2月, 2016 12 次提交
-
-
由 Mátyás Mustoha 提交于
-
由 Michael Huynh 提交于
Fixes several minor spelling errors and includes a suggested style fix.
-
由 petevine 提交于
-
由 bors 提交于
A quick fix for several issues that break a Solaris/Illumos build. Also, adds a CPU target specification (as seen in a patch for OpenBSD #31727).
-
由 bors 提交于
The standard library doesn't depend on rustc_bitflags, so move it to explicit dependencies on all other crates. Additionally, the arena/fmt_macros deps could be dropped from libsyntax.
-
由 bors 提交于
Android should use 64-bit LFS symbols for `lseek` and `ftruncate`, lest those offset parameters suffer a lossy cast down to a 32-bit `off_t`. Unlike GNU/Linux, Android's `stat`, `dirent`, and related functions are always 64-bit LFS compatible, and `open` already implies `O_LARGEFILE`, so all those don't need to follow Linux. It might be nice to unify them anyway, but those other LFS symbols aren't present in API 18 bionic. r? @alexcrichton
-
由 bors 提交于
`to_lowercase` example mistakenly calls `to_uppercase` function. This fixes the example.
-
由 bors 提交于
Some struct members have a slighty different name on NetBSD. This has been fixed in the libc crate, but not in libstd, breaking the NetBSD build. Related C struct definition: http://nxr.netbsd.org/xref/src/sys/sys/stat.h?r=1.68#59 This also removes the broken `st_spare()` from MetadataExt, since it is private field reserved for future use. @dhuseby In case this conflicts with any of your pending patches, feel free to intervene - I'm happy to withdraw this PR. r? @alexcrichton
-
由 Nikita Baksalyar 提交于
-
由 Paul Dicker 提交于
-
由 bors 提交于
With these changes you can build a freestanding sysroot without using floating points using a Cargo.toml and copying the `deps` folder cargo outputs. ``` [package] name = "sysroot" version = "0.1.0" [lib] path = "lib.rs" crate-type = ["rlib"] [dependencies.core] path = "../vendor/rust/src/src/libcore" features = ["disable_float"] [dependencies] collections = { path = "../vendor/rust/src/src/libcollections" } ```
-
由 Alex Crichton 提交于
The standard library doesn't depend on rustc_bitflags, so move it to explicit dependencies on all other crates. Additionally, the arena/fmt_macros deps could be dropped from libsyntax.
-