- 06 8月, 2013 2 次提交
- 05 8月, 2013 36 次提交
-
-
由 bors 提交于
It was previously pushing the byte on top of the string's null terminator. I added a test to make sure it doesn't break in the future.
-
由 bors 提交于
It seems that relatively new code uses `Foo::new()` instead of `Foo()` so I wrote a patch to migrate some structs to the former style. Is it a right direction? If there are any guidelines not to use new()-style, could you add them to the [style guide](https://github.com/omasanori/rust/wiki/Note-style-guide)?
-
由 bors 提交于
Useful for SDL and possibly Android too. r? @brson
-
由 bors 提交于
-
由 OGINO Masanori 提交于
Signed-off-by: NOGINO Masanori <masanori.ogino@gmail.com>
-
由 bors 提交于
-
由 Brian Anderson 提交于
-
由 bors 提交于
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
The truncation needs to be done in the console logger in order to catch all the logging output, and because truncation only matters when outputting to the console.
-
由 bors 提交于
Update the arm linux support some more. We had a previous patch for the RasberryPi. This adds a new target `arm-unknown-linux-gnueabi` for more general arm linux support. Build/Host machine: x86_64 Debian testing (jessie) with the `gcc-4.4-arm-linux-gnueabi` package Tested on targets: - TS-7800 Feroceon (ARMv5TEJ) running Debian 7.0 wheezy - Beaglebone black (ARMv7) running Angstrom GNU/Linux v2012.12 - rustc flags: `--target=arm-unknown-linux-gnueabi --linker=arm-linux-gnueabi-gcc` - Samsung Galaxy S II (to make sure android still works) - rustc flags: `--target=arm-linux-androideabi --android-cross-path=[path to standalone toolchain]` Since not all arm devices (i.e. afaik anything older than armv6 like the ts-7800 i tested on) supported getting the tls address via the `mrc` instruction, I made it also try via the magic address the kernel maps into the address space (0xFFFF0FF0). One or the other should work (and on android it seems like both work). Also fixes a bug where rustc would always try to invoke the android assembler for any kind of arm target.
-
由 bors 提交于
The compiler-generated dtor for DList recurses deeply to drop Nodes. For big lists this can overflow the stack. This is a problem for the new scheduler, where split stacks are not implemented. Thanks @blake2-ppc
-
由 Brian Anderson 提交于
The compiler-generated dtor for DList recurses deeply to drop Nodes. For big lists this can overflow the stack.
-
由 bors 提交于
-
由 Luqman Aden 提交于
-
由 bors 提交于
These are both obsoleted by the forthcoming new GC.
-
由 Dmitry Ermolov 提交于
-
由 Dmitry Ermolov 提交于
Closes #5506.
-
由 Daniel Micay 提交于
-
由 Brian Anderson 提交于
Not compatible with newsched
-
由 Brian Anderson 提交于
This is no longer testable once newsched is turned on
-
由 Brian Anderson 提交于
Every time run_sched_once performs a 'scheduling action' it needs to guarantee that it runs at least one more time, so enqueue another run_sched_once callback. The primary reason it needs to do this is because not all async callbacks are guaranteed to run, it's only guaranteed that *a* callback will run after enqueing one - some may get dropped. At the moment this means we wastefully create lots of callbacks to ensure that there will *definitely* be a callback queued up to continue running the scheduler. The logic really needs to be tightened up here.
-
由 Brian Anderson 提交于
rustc needs *even more* megabytes when run without optimizations
-
由 Brian Anderson 提交于
Otherwise interferes with the existing runtime
-
由 Brian Anderson 提交于
Also fix some incorrect comments and variable names.
-
由 bors 提交于
WIth this patch `RUSTFLAGS='--cfg unicode' make check"` passed successfully. * Why doesn't `#[link_name="icuuc"]` make libextra to link against libicuuc.so? * In `extra::unicode::tests`, `use unicode; unicode::is_foo('a')` failed but `use unicode::*; is_foo('a')` succeeded. Is it right?
-
由 Steven Fackler 提交于
It was previously pushing the byte on top of the string's null terminator. I added a test to make sure it doesn't break in the future.
-
由 bors 提交于
This is a reopening of #6713 This is still blocked on windows failures. I'll re-push try once the existing crisis has passed.
-
由 Daniel Micay 提交于
etc: add the `in` keyword to the emacs mode.
-
由 Alex Crichton 提交于
Thanks @luqama!
-
由 Alex Crichton 提交于
-
由 Alex Crichton 提交于
At the same time create a more robust wrapper to try to prevent this type of issue from cropping up in the future.
-
由 Alex Crichton 提交于
* LLVM now has a C interface to LLVMBuildAtomicRMW * The exception handling support for the JIT seems to have been dropped * Various interfaces have been added or headers have changed
-
由 Alex Crichton 提交于
-
由 Brian Anderson 提交于
-
由 bors 提交于
rvalues aren't going to be used anywhere but as the argument, so there's no point in copying them. LLVM used to eliminate the copy later, but why bother emitting it in the first place?
-
- 04 8月, 2013 2 次提交
-
-
由 bors 提交于
multicast functions now take IpAddr (without port), because they dont't need port. Uv* types renamed: * UvIpAddr -> UvSocketAddr * UvIpv4 -> UvIpv4SocketAddr * UvIpv6 -> UvIpv6SocketAddr "Socket address" is a common name for (ip-address, port) pair (e.g. in sockaddr_in struct). P. S. Are there any backward compatibility concerns? What is std::rt module, is it a part of public API?
-
由 bors 提交于
Use unchecked vec indexing since the vector bounds are checked by the loop. Iterators are not easy to use in this case since we skip 1-4 bytes each lap. This part of the commit speeds up is_utf8 for ASCII input. Check codepoint ranges by checking the byte ranges manually instead of computing a full decoding for multibyte encodings. This is easy to read and corresponds to the UTF-8 syntax in the RFC. No changes to what we accept. A comment notes that surrogate halves are accepted. Before: test str::bench::is_utf8_100_ascii ... bench: 165 ns/iter (+/- 3) test str::bench::is_utf8_100_multibyte ... bench: 218 ns/iter (+/- 5) After: test str::bench::is_utf8_100_ascii ... bench: 130 ns/iter (+/- 1) test str::bench::is_utf8_100_multibyte ... bench: 156 ns/iter (+/- 3) An improvement upon the previous pull #8133
-