about summary refs log tree commit diff
path: root/src/librustc_driver
AgeCommit message (Collapse)AuthorLines
2018-03-20rename epoch to editionKurtis Nusbaum-1/+1
2018-03-20Reinit the stack guard on unexpected failureTatsuyuki Ishi-3/+3
2018-03-20Implement some trivial size_hints for various iteratorsPhlosioneer-0/+7
This also implements ExactSizeIterator where applicable. Addresses most of the Iterator traits mentioned in #23708.
2018-03-20Rollup merge of #49092 - mark-i-m:deptrack_readme, r=nikomatsakiskennytm-4/+2
Replace many of the last references to readmes In particular, this removes the dep track readme, so it should not be merged before https://github.com/rust-lang-nursery/rustc-guide/pull/92 Fix #47935 cc #48478 r? @nikomatsakis
2018-03-19Address review commentsTatsuyuki Ishi-3/+5
2018-03-18rustc_driver: get rid of extra thread on WindowsTatsuyuki Ishi-1/+5
2018-03-18rustc_driver: get rid of extra thread on UnixTatsuyuki Ishi-8/+43
2018-03-18Auto merge of #48985 - scalexm:lowering, r=nikomatsakisbors-0/+4
MVP for chalkification r? @nikomatsakis
2018-03-17AST/HIR: Clarify what the optional name in extern crate items meanVadim Petrochenkov-1/+1
2018-03-17Auto merge of #49106 - kennytm:rollup, r=kennytmbors-4/+6
Rollup of 8 pull requests - Successful merges: #48943, #48960, #48983, #49055, #49057, #49077, #49082, #49083 - Failed merges:
2018-03-17Auto merge of #48904 - Zoxc:code-and-file-maps, r=michaelwoeristerbors-2/+2
Make CodeMap and FileMap thread-safe r? @michaelwoerister
2018-03-16Replace many of the last references to readmesMark Mansi-4/+2
2018-03-16Always print `aborting due to n previous error(s)` and only print it once ↵John Kåre Alsaker-24/+30
for multi-threaded code
2018-03-16Checks for unknown attributes before abortingShotaro Yamada-4/+6
...due to unresolved macros.
2018-03-16Rollup merge of #48706 - ehuss:main-not-found-in-crate, r=estebankkennytm-1/+1
Add crate name to "main function not found" error message. Fixes #44798 and rust-lang/cargo#4948. I was wondering if it might be cleaner to update the ui tests to add a simple `fn main() {}` for the unrelated tests. Let me know if you would prefer that.
2018-03-14Auto merge of #47630 - canndrew:exhaustive-patterns, r=nikomatsakisbors-5/+5
Stabilise feature(never_type). Introduce feature(exhaustive_patterns) This stabilizes `!`, removing the feature gate as well as the old defaulting-to-`()` behavior. The pattern exhaustiveness checks which were covered by `feature(never_type)` have been moved behind a new `feature(exhaustive_patterns)` gate.
2018-03-15Require a thread-safe file loaderJohn Kåre Alsaker-2/+2
2018-03-14Add crate name to "main function not found" error message.Eric Huss-1/+1
Fixes #44798 and rust-lang/cargo#4948.
2018-03-15Rollup merge of #48993 - alexheretic:fix-48816, r=michaelwoeristerkennytm-0/+6
fix #48816 don't print help on indirect compiler ICE https://github.com/rust-lang/rust/issues/48816#issuecomment-372817573
2018-03-15Rollup merge of #48765 - Phlosioneer:10234-wall-help-message, r=estebankkennytm-0/+16
Add info message for -Wall command Users coming from other languages (namely C and C++) often expect to use a -Wall flag. Rustc doesn't support that, and previously it simply printed that it didn't recognize the "all" lint. This change makes rustc print out a help message, explaining: - Why there is no -Wall flag - How to view all the available warnings - Point out that the most commonly used warning is -Wunused - Instead of using a command-line flag, the user should consider a !#[warn(unused)] directive in the root of their crate. I tried to keep the language consistent with the other usage help. Comment if I should change anything. closes #10234, if accepted.
2018-03-14Move code into librustc_traitsscalexm-1/+3
2018-03-14Address niko's nitsscalexm-1/+1
2018-03-14Add MVP for chalkificationscalexm-0/+2
2018-03-14Remove syntax and syntax_pos thread localsJohn Kåre Alsaker-1/+23
2018-03-14remove defaulting to unitAndrew Cann-5/+5
Types will no longer default to `()`, instead always defaulting to `!`. This disables the associated warning and removes the flag from TyTuple
2018-03-13fix #48816 don't print help on indirect compiler ICEAlex Butler-0/+6
2018-03-13introduce `infcx.at(..).normalize(..)` operation [VIC]Niko Matsakis-0/+4
It is backed by the new `normalize_projection_ty` query, which uses canonicalization.
2018-03-13refactor `ParamEnv::empty(Reveal)` into two distinct methodsNiko Matsakis-2/+2
- `ParamEnv::empty()` -- does not reveal all, good for typeck - `ParamEnv::reveal_all()` -- does, good for trans - `param_env.with_reveal_all()` -- converts an existing parameter environment
2018-03-12Update -Wall message based on feedbackPhlosioneer-4/+3
The reference to -Wunused was removed, and some phrasing was changed.
2018-03-09Move PROFQ_CHAN to a Session fieldJohn Kåre Alsaker-51/+46
2018-03-08Make it possible to ungate features by epochManish Goregaokar-1/+3
2018-03-08Regenerate testsOliver Schneider-1/+1
2018-03-08rustc_passes::consts -> rvalue_promotionOliver Schneider-2/+2
2018-03-08Merge const linting pass into const propOliver Schneider-7/+0
2018-03-08Move the pattern checking code to hairOliver Schneider-1/+1
2018-03-08The `const_eval` module is no moreOliver Schneider-3/+2
2018-03-08Allow tools (e.g. miri) to enable rust loggingOliver Schneider-1/+7
2018-03-08Nuke the entire ctfe from orbit, it's the only way to be sureOliver Schneider-0/+7
2018-03-08Move librustc_const_eval to librustc_mirOliver Schneider-5/+1
2018-03-06Fix trailing whitespacePhlosioneer-1/+1
2018-03-06Update env_logger to 0.5.4Alex Crichton-2/+2
It looks like this cuts down on the number of dependencies in env_logger and notably cuts out a difference between a shared dependency of rls/cargo. My goal here is to ensure that when we compile the RLS/Cargo on CI we only compile Cargo once, and this is one step towards that!
2018-03-06Add info message for -Wall commandPhlosioneer-0/+17
Users coming from other languages (namely C and C++) often expect to use a -Wall flag. Rustc doesn't support that, and previously it simply printed that it didn't recognize the "all" lint. This change makes rustc print out a help message, explaining: - Why there is no -Wall flag - How to view all the available warnings - Point out that the most commonly used warning is -Wunused - Instead of using a command-line flag, the user should consider a !#[warn(unused)] directive in the root of their crate.
2018-03-05Turn features() into a query.Michael Woerister-6/+6
2018-03-04Rollup merge of #48664 - Keruspe:codegen, r=alexcrichtonkennytm-1/+3
make codegen-backends directory name configurable This allows to parallel-install several versions of rust system-wide Fixes #48263
2018-03-02make codegen-backends directory name configurableMarc-Antoine Perennou-1/+3
This allows to parallel-install several versions of rust system-wide Fixes #48263 Signed-off-by: Marc-Antoine Perennou <Marc-Antoine@Perennou.com>
2018-03-02Replace Rc with Lrc for shared dataJohn Kåre Alsaker-9/+9
2018-03-01fix tests in `librustc_driver`Niko Matsakis-1/+2
2018-02-28Rollup merge of #48461 - Manishearth:epoch-dyn-trait, r=nmatsakisManish Goregaokar-11/+11
Fixes #47311. r? @nrc
2018-02-28Rollup merge of #48266 - pietroalbini:report-compiler-flags-on-ice, ↵kennytm-5/+80
r=michaelwoerister Report non-standard compile flags on ICE Some ICEs (such as the recent #48248) only happens when a non-standard compiler flag is provided to rustc, but users don't always report the used flags. This can slow down reproducing the issue, so this PR shows all the non-standard compiler flags in the ICE error message. For example, the output of #48248 with this PR is: ``` error: internal compiler error: [...] thread 'rustc' panicked at [...] note: Run with `RUST_BACKTRACE=1` for a backtrace. note: the compiler unexpectedly panicked. this is a bug. note: we would appreciate a bug report: [...] note: rustc 1.25.0-dev running on x86_64-unknown-linux-gnu note: compiler flags: -C link-dead-code ``` ### Open questions * At the moment, only `-C` and `-Z` flags are shown by default, and all the ones provided by cargo in a standard build are ignored: I did this to only show the flags that probably caused the ICE, and to remove some noise from the message. This removed flags like `opt-level` and `debuginfo` though, could those be useful for reproducing ICEs?
2018-02-24Rollup merge of #48452 - varkor:unpacked-kind, r=eddybManish Goregaokar-4/+4
Introduce UnpackedKind This adds an `UnpackedKind` type as a typesafe counterpart to `Kind`. This should make future changes to kinds (such as const generics!) more resilient, as the type-checker will be able to catch more potential issues. r? @eddyb cc @yodaldevoid