summary refs log tree commit diff
path: root/src/librustc_driver/lib.rs
AgeCommit message (Collapse)AuthorLines
2016-06-30Remove `after_expand` and `after_write_deps` CompileController entry pointsJeffrey Seyfried-1/+1
2016-06-23Move errors from libsyntax to its own crateJonathan Turner-11/+14
2016-05-25trans: save metadata even with -Z no-trans.Eduard Burtescu-4/+0
2016-05-18thread the DepGraph to session/crate-storeNiko Matsakis-4/+11
This is a [breaking-change] for plugin authors. You must now create a dep-graph earlier.
2016-05-10Also rename the print_from_ast.Pavel Sountsov-11/+11
2016-05-10Rename after_ast to after_hir_lowering.Pavel Sountsov-2/+2
2016-05-10Make --emit dep-info work correctly with -Z no-analysis again.Pavel Sountsov-13/+13
Previously, it would attempt to resolve some external crates that weren't necessary for dep-info output. Fixes #33231.
2016-05-09Reimplement pretty printingJeffrey Seyfried-0/+2
2016-05-08Auto merge of #33091 - sanxiyn:unused-trait-import-3, r=nrcbors-1/+0
Warn unused trait imports, rebased Rebase of #30021. Fix #25730.
2016-05-03Remove unused trait imports flagged by lintSeo Sanghyeon-1/+0
2016-05-02Auto merge of #33119 - nrc:pretty, r=pnkfelixbors-54/+63
Refactor pretty printing to use the compiler API
2016-05-03rebasingNick Cameron-1/+0
Note that this whole PR is a [breaking-change] for clients of the Compiler API.
2016-05-03Fix testsNick Cameron-1/+4
2016-05-03Refactor pretty printing to use more of the driverNick Cameron-11/+33
2016-05-03Use the compiler API to run pretty printing.Nick Cameron-53/+39
This commit still does a lot of building in pretty because we always run after parsing.
2016-05-03Make pretty printer take Session by refNick Cameron-3/+2
2016-05-02fix rebase flawsNiko Matsakis-3/+2
2016-05-02refactor to use new snippet code and modelNiko Matsakis-7/+9
Major changes: - Remove old snippet rendering code and use the new stuff. - Introduce `span_label` method to add a label - Remove EndSpan mode and replace with a fn to get the last character of a span. - Stop using `Option<MultiSpan>` and just use an empty `MultiSpan` - and probably a bunch of other stuff :)
2016-05-01Avoid using the lowering context in `librustc_save_analysis`Jeffrey Seyfried-1/+0
2016-05-01Remove rust flags from doc blockGuillaume Gomez-1/+7
2016-04-28Auto merge of #33217 - aochagavia:fileloader, r=nrcbors-9/+21
rustc_driver: Allow running the compiler with a FileLoader cc @nrc. I chose to implement this in such a way that it doesn't break anything. Please let me know if you want me to change anything.
2016-04-27rustc_driver: Allow running the compiler with a FileLoaderAdolfo Ochagavía-9/+21
2016-04-26save-analysis-json: thread through -z optionNick Cameron-2/+18
In fact, we make JSOn the default and add an option for save-analysis-csv for the legacy behaviour. We also rename some bits and pieces `dxr` -> `save-analysis`
2016-04-20debugging, misc fixesNick Cameron-8/+3
2016-04-07Auto merge of #32016 - nikomatsakis:incr-comp-save, r=mwbors-0/+1
Save/load incremental compilation dep graph Contains the code to serialize/deserialize the dep graph to disk between executions. We also hash the item contents and compare to the new hashes. Also includes a unit test harness. There are definitely some known limitations, such as https://github.com/rust-lang/rust/issues/32014 and https://github.com/rust-lang/rust/issues/32015, but I am leaving those for follow-up work. Note that this PR builds on https://github.com/rust-lang/rust/pull/32007, so the overlapping commits can be excluded from review. r? @michaelwoerister
2016-04-06Auto merge of #32230 - GuillaumeGomez:extend_css, r=alexcrichtonbors-49/+4
Add --extend-css option to rustdoc Fixes #32223 r? @brson
2016-04-06make an incremental crateNiko Matsakis-0/+1
for now, this houses `svh` and the code to check `assert_dep_graph` is sane
2016-04-06rustc: move rustc_front to rustc::hir.Eduard Burtescu-1/+0
2016-04-05Centralize nightly compiler flags handlingGuillaume Gomez-49/+4
2016-03-31allow RUST_BACKTRACE=0 to act as if unsetEmanuel Czirai-1/+4
/# This is a combination of 16 commits. /# The first commit's message is: allow RUST_BACKTRACE=disabled to act as if unset When RUST_BACKTRACE is set to "disabled" then this acts as if the env. var is unset. /# This is the 2nd commit message: case insensitive "DiSaBLeD" RUST_BACKTRACE value previously it expected a lowercase "disabled" to treat the env. var as unset /# This is the 3rd commit message: RUST_BACKTRACE=0 acts as if unset previously RUST_BACKTRACE=disabled was doing the same thing /# This is the 4th commit message: RUST_BACKTRACE=0|n|no|off acts as if unset previously only RUST_BACKTRACE=0 acted as if RUST_BACKTRACE was unset Now added more options (case-insensitive): 'n','no' and 'off' eg. RUST_BACKTRACE=oFF /# This is the 5th commit message: DRY on the value of 2 DRY=don't repeat yourself Because having to remember to keep the two places of '2' in sync is not ideal, even though this is a simple enough case. /# This is the 6th commit message: Revert "DRY on the value of 2" This reverts commit 95a0479d5cf72a2b2d9d21ec0bed2823ed213fef. Nevermind this DRY on 2, because we already have a RY on 1, besides the code is less readable this way... /# This is the 7th commit message: attempt to document unsetting RUST_BACKTRACE /# This is the 8th commit message: curb allocations when checking for RUST_BACKTRACE this means we don't check for case-insensitivity anymore /# This is the 9th commit message: as decided, RUST_BACKTRACE=0 turns off backtrace /# This is the 10th commit message: RUST_TEST_NOCAPTURE=0 acts as if unset (that is, capture is on) Any other value acts as if nocapture is enabled (that is, capture is off) /# This is the 11th commit message: update other RUST_TEST_NOCAPTURE occurrences apparently only one place needs updating /# This is the 12th commit message: update RUST_BACKTRACE in man page /# This is the 13th commit message: handle an occurrence of RUST_BACKTRACE /# This is the 14th commit message: ensure consistency with new rules for backtrace /# This is the 15th commit message: a more concise comment for RUST_TEST_NOCAPTURE /# This is the 16th commit message: update RUST_TEST_NOCAPTURE in man page
2016-03-30move `const_eval` and `check_match` out of `librustc`Oliver Schneider-0/+2
2016-03-29Remove unnecessary dependencies on rustc_llvm.Eduard Burtescu-0/+4
2016-03-27rustc_trans: move save to librustc_save_analysis.Eduard Burtescu-1/+2
2016-03-25Compute a salt from arguments passed via -Cmetadata.Michael Woerister-2/+0
2016-03-22sprinkle feature gates here and thereJorge Aparicio-0/+1
2016-03-20Utilize `if..let` over single `match` branch.Corey Farwell-33/+28
2016-03-20Remove double-negative conditionals.Corey Farwell-6/+6
2016-03-20Replace unneeded owned `Vec` usage with `slice`.Corey Farwell-3/+3
2016-03-14Allow custom filenames for anonymous inputsmitaa-5/+6
2016-03-09Auto merge of #31631 - jonas-schievink:agoraphobia, r=nrcbors-6/+17
[breaking-batch] Move more uses of `panictry!` out of libsyntax
2016-03-03Hide gated cfg attributes from the output of `--print cfg`Andrea Canciani-1/+10
Gated cfg attributes are not available on the stable and beta release channels, therefore they should not be presented to users of those channels in order to avoid confusion.
2016-03-02Build the same configuration when compiling and for `--print cfg`Andrea Canciani-1/+3
The configuration returned by `config::build_configuration` needs to be modified with `target_features::add_configuration` in order to also contain the target features. This is already done for the configuration used when compiling and when creating the documentation, but was missing in the `cfg` printing code.
2016-02-24rustc: Refactor how unstable flags are handledAlex Crichton-52/+98
This commit adds support for *truly* unstable options in the compiler, as well as adding warnings for the start of the deprecation path of unstable-but-not-really options. Specifically, the following behavior is now in place for handling unstable options: * As before, an unconditional error is emitted if an unstable option is passed and the `-Z unstable-options` flag is not present. Note that passing another `-Z` flag does not require passing `-Z unstable-options` as well. * New flags added to the compiler will be in the `Unstable` category as opposed to the `UnstableButNotReally` category which means they will unconditionally emit an error when used on stable. * All current flags are in a category where they will emit warnings when used that the option will soon be a hard error. Also as before, it is intended that `-Z` is akin to `#![feature]` in a crate where it is required to unlock unstable functionality. A nightly compiler which is used without any `-Z` flags should only be exercising stable behavior.
2016-02-19Do less panicking in generalJonas Schievink-1/+13
2016-02-16Move more uses of `panictry!` out of libsyntaxJonas Schievink-6/+5
[breaking-change] for syntax extensions
2016-02-13Auto merge of #31358 - japaric:print-targets, r=alexcrichtonbors-0/+5
that prints a list of all the triples supported by the `--target` flag r? @alexcrichton
2016-02-13Auto merge of #31524 - jonas-schievink:autoderef, r=steveklabnikbors-1/+1
2016-02-12Use more autoderef in rustc_driverJonas Schievink-1/+1
2016-02-12Auto merge of #30726 - GuillaumeGomez:compile-fail, r=brsonbors-1/+1
r? @brson cc @alexcrichton I still need to add error code explanation test with this, but I can't figure out a way to generate the `.md` files in order to test example source codes. Will fix #27328.
2016-02-12rustc: add a `--print target-list` commandJorge Aparicio-0/+5
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-07-14 05:57:37 +0000