- 07 1月, 2018 9 次提交
-
-
由 Malo Jaffré 提交于
Upgrade `log` to `0.4` in multiple crates.
-
由 Björn Steinbrink 提交于
-
由 Björn Steinbrink 提交于
Refs #46437 as it also removes LLVMRustWriteDebugLocToString()
-
由 Björn Steinbrink 提交于
Refs #46437
-
由 Björn Steinbrink 提交于
The same effect can be achieved using -Cllvm-args=-debug Refs #46437 as it removes LLVMRustSetDebug()
-
由 keatinge 提交于
-
由 keatinge 提交于
-
由 Zack M. Davis 提交于
This `horizontal_trim` function strips the leading whitespace from doc-comments that have a left-asterisk-margin: /** * You know what I mean— * * comments like this! */ The index of the column of asterisks is `i`, and if trimming is deemed possible, we slice each line from `i+1` to the end of the line. But if, in particular, `i` was 0 _and_ there was an empty line (as in the example given in the reporting issue), we ended up panicking trying to slice an empty string from 0+1 (== 1). Let's tighten our check to say that we can't trim when `i` is even the same as the length of the line, not just when it's greater. (Any such cases would panic trying to slice `line` from `line.len()+1`.) Resolves #47197.
-
由 keatinge 提交于
-
- 06 1月, 2018 10 次提交
-
-
由 keatinge 提交于
-
由 keatinge 提交于
-
由 keatinge 提交于
-
由 keatinge 提交于
-
由 Sam 提交于
-
由 Manish Goregaokar 提交于
-
由 Manish Goregaokar 提交于
-
由 Ed Schouten 提交于
Ideally, we should make use of CloudABI's internal proc_raise(SIGABRT) system call. POSIX abort() requires things like flushing of stdios, which may not be what we want under panic conditions. Invoking the raw CloudABI system call would have prevented that. Unfortunately, we have to make use of the "cloudabi" crate to invoke raw CloudABI system calls. This is undesired, as discussed in the pull request (#47190).
-
由 Alex Crichton 提交于
This showed up on the Windows bot for testing this PR, and this pr allows `mark_incr_comp_session_as_invalid` ok if it's already invalid, hopefully avoiding scary ICEs and instead leaving the nicely printed errors
-
由 Simonas Kazlauskas 提交于
This is only applicable when neither of --emit=llvm-ir or --emit=llvm-bc are not requested. In case either of these outputs are wanted, but the benefits of such context are desired as well, -Zfewer_names option provides the same functionality regardless of the outputs requested.
-
- 05 1月, 2018 10 次提交
-
-
由 Stjepan Glavina 提交于
-
由 Sergio Benitez 提交于
-
由 Sam 提交于
-
由 Eduard-Mihai Burtescu 提交于
-
由 Guillaume Gomez 提交于
-
由 Esteban Küber 提交于
-
由 Matt Brubeck 提交于
-
由 Alex Crichton 提交于
I forgot to update the bootstrap compiler for the 1.23.0 release so let's make sure it doesn't happen again!
-
由 Loïc Damien 提交于
-
由 Ed Schouten 提交于
CloudABI uses LLVM's libunwind for stack unwinding. There was a small bug that went by unnoticed, namely that it was not built with -fno-rtti. This caused it to (indirectly) depend on the entire C++ runtime. Now that that issue has been resolved, it is also perfectly fine to make use of this library for programming languages other than C++.
-
- 04 1月, 2018 11 次提交
-
-
由 Alex Crichton 提交于
These no longer work now that Cargo changes the cwd of rustc while it's running. Instead use an absolute path that's set by rustbuild.
-
由 Alex Crichton 提交于
* Bump the release version to 1.25 * Bump the bootstrap compiler to the recent beta * Allow using unstable rustdoc features on beta - this fix has been applied to the beta branch but needed to go to the master branch as well.
-
由 aheart 提交于
The example with the ? operator was missing file.write_all
-
由 Michael Woerister 提交于
-
由 Michael Woerister 提交于
This mirrors what we for stabilizing the incr. comp. cache and is necessary for reproducible builds.
-
由 Sebastian Dröge 提交于
-
由 Michael Woerister 提交于
-
由 Björn Steinbrink 提交于
-
由 Björn Steinbrink 提交于
Refs #46437
-
由 Björn Steinbrink 提交于
The function was added as a wrapper to handle compatibility with older LLVM versions that we no longer support, so it can be removed. Refs #46437
-
由 Esteban Küber 提交于
-