rust/src/librustc_interface/interface.rs, branch perf-tmphttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=perf-tmp2020-08-30T15:45:07+00:00mv compiler to compiler/2020-08-30T15:45:07+00:00markmarkm@cs.wisc.edu2020-08-28T03:58:48+00:00urn:sha1:9e5f7d5631b8f4009ac1c693e585d4b7108d4275rust_ast::ast => rustc_ast2020-08-17T20:32:32+00:00Ujjwal Sharmaryzokuken@disroot.org2020-04-27T17:56:11+00:00urn:sha1:a888b02884883de41d0ce08aa62a6cd6d4790951replaced log with tracing2020-08-15T20:03:11+00:00Gurpreet Singhgdhuper@gmail.com2020-08-14T06:05:01+00:00urn:sha1:d2753f91b5e09a91841fa729ef6b14d7ef249e8aEliminate the `SessionGlobals` from `librustc_ast`.2020-08-08T02:03:42+00:00Nicholas Nethercotennethercote@mozilla.com2020-07-30T01:27:50+00:00urn:sha1:e539dd65f8ba80837f7477c0547c61514bceb3ad
By moving `{known,used}_attrs` from `SessionGlobals` to `Session`. This
means they are accessed via the `Session`, rather than via TLS. A few
`Attr` methods and `librustc_ast` functions are now methods of
`Session`.
All of this required passing a `Session` to lots of functions that didn't
already have one. Some of these functions also had arguments removed, because
those arguments could be accessed directly via the `Session` argument.
`contains_feature_attr()` was dead, and is removed.
Some functions were moved from `librustc_ast` elsewhere because they now need
to access `Session`, which isn't available in that crate.
- `entry_point_type()` --> `librustc_builtin_macros`
- `global_allocator_spans()` --> `librustc_metadata`
- `is_proc_macro_attr()` --> `Session`
Remove `setup_callbacks_and_run_in_default_thread_pool_with_globals()`.2020-08-05T00:42:45+00:00Nicholas Nethercotennethercote@mozilla.com2020-08-03T23:42:14+00:00urn:sha1:af4e3e08ea3d9739e5af541b737527584cea1d8f
It's a very thin wrapper around
`setup_callbacks_and_run_in_thread_pool_with_globals()` and it has a
single call site.
Change some function names.2020-07-10T06:07:20+00:00Nicholas Nethercotennethercote@mozilla.com2020-07-07T03:41:08+00:00urn:sha1:bf7078615b868f7359bff58933fd5236fabe7280
A couple of these are quite long, but they do a much better job of
explaining what they do, which was non-obvious before.
Rollup merge of #74079 - nnethercote:session-globals, r=nikomatsakis2020-07-09T18:50:32+00:00Manish Goregaokarmanishsmail@gmail.com2020-07-09T18:50:32+00:00urn:sha1:89c9e970ddbe47622bcc52b135d35508510daa55
Eliminate confusing "globals" terminology.
There are some structures that are called "globals", but are they global
to a compilation session, and not truly global. I have always found this
highly confusing, so this commit renames them as "session globals" and
adds a comment explaining things.
Also, the commit fixes an unnecessary nesting of `set()` calls
`src/librustc_errors/json/tests.rs`
r? @Aaron1011
Eliminate confusing "globals" terminology.2020-07-09T04:11:44+00:00Nicholas Nethercotennethercote@mozilla.com2020-07-06T00:53:14+00:00urn:sha1:81c5bb6a3fb02d1c1c3a4698e9e0e031ef2f4e4e
There are some structures that are called "globals", but are they global
to a compilation session, and not truly global. I have always found this
highly confusing, so this commit renames them as "session globals" and
adds a comment explaining things.
Also, the commit fixes an unnecessary nesting of `set()` calls
`src/librustc_errors/json/tests.rs`
Use for<'tcx> fn pointers in Providers, instead of having Providers<'tcx>.2020-07-05T20:00:14+00:00Eduard-Mihai Burtescuedy.burt@gmail.com2020-07-05T20:00:14+00:00urn:sha1:f07100afc8650101ac924d728521e1a5d0ce9080Fix -Z unpretty=everybody_loops2020-06-20T00:27:22+00:00Joshua Nelsonjyn514@gmail.com2020-06-20T00:06:49+00:00urn:sha1:95f8daa82b52e95081b66d58953c2329a9f0458e
It turns out that this has not been working for who knows how long.
Previously:
```
pub fn h() { 1 + 2; }
```
After this change:
```
pub fn h() { loop {} }
```
This only affected the pass when run with the command line
pretty-printing option, so rustdoc was still replacing bodies with
`loop {}`.