- 02 9月, 2021 6 次提交
- 28 8月, 2021 1 次提交
-
-
由 inquisitivecrystal 提交于
-
- 23 8月, 2021 1 次提交
-
-
由 Frank Steffahn 提交于
-
- 22 8月, 2021 3 次提交
-
-
由 Frank Steffahn 提交于
-
由 Frank Steffahn 提交于
-
由 Aaron Hill 提交于
Instead of updating global state to mark attributes as used, we now explicitly emit a warning when an attribute is used in an unsupported position. As a side effect, we are to emit more detailed warning messages (instead of just a generic "unused" message). `Session.check_name` is removed, since its only purpose was to mark the attribute as used. All of the callers are modified to use `Attribute.has_name` Additionally, `AttributeType::AssumedUsed` is removed - an 'assumed used' attribute is implemented by simply not performing any checks in `CheckAttrVisitor` for a particular attribute. We no longer emit unused attribute warnings for the `#[rustc_dummy]` attribute - it's an internal attribute used for tests, so it doesn't mark sense to treat it as 'unused'. With this commit, a large source of global untracked state is removed.
-
- 16 8月, 2021 1 次提交
-
-
由 Aaron Hill 提交于
Fixes #85019 A `SourceFile` created during compilation may have a relative path (e.g. if rustc itself is invoked with a relative path). When we write out crate metadata, we convert all relative paths to absolute paths using the current working direction. However, the working directory is not included in the crate hash. This means that the crate metadata can change while the crate hash remains the same. Among other problems, this can cause a fingerprint mismatch ICE, since incremental compilation uses the crate metadata hash to determine if a foreign query is green. This commit moves the field holding the working directory from `Session` to `Options`, including it as part of the crate hash.
-
- 10 8月, 2021 1 次提交
-
-
由 bjorn3 提交于
-
- 08 8月, 2021 1 次提交
-
-
由 12101111 提交于
-
- 06 8月, 2021 1 次提交
-
-
由 Ellen 提交于
-
- 04 8月, 2021 1 次提交
-
-
由 Amanieu d'Antras 提交于
This was removed by #85284 in favor of -Zprofiler-runtime=<name>. However the suggested -Zprofiler-runtime=None doesn't work because "None" is treated as a crate name.
-
- 30 7月, 2021 1 次提交
-
-
由 Jade 提交于
Since RFC 3052 soft deprecated the authors field anyway, hiding it from crates.io, docs.rs, and making Cargo not add it by default, and it is not generally up to date/useful information, we should remove it from crates in this repo.
-
- 25 7月, 2021 2 次提交
-
-
由 Camille GILLOT 提交于
-
由 Camille GILLOT 提交于
-
- 24 7月, 2021 1 次提交
-
-
由 Joshua Nelson 提交于
Previously, this would change the test output when RUSTUP_HOME was set: ``` ---- [ui] ui/issues/issue-49851/compiler-builtins-error.rs stdout ---- diff of stderr: 1 error[E0463]: can't find crate for `core` 2 | 3 = note: the `thumbv7em-none-eabihf` target may not be installed + = help: consider downloading the target with `rustup target add thumbv7em-none-eabihf` 4 5 error: aborting due to previous error 6 ``` Originally, I fixed it by explicitly unsetting RUSTUP_HOME in compiletest. Then I realized that almost no one has RUSTUP_HOME set, since rustup doesn't set it itself; although it does set RUST_RECURSION_COUNT whenever it launches a proxy. Then it was pointed out that this runtime check doesn't really make sense and it's fine to make it unconditional.
-
- 18 7月, 2021 6 次提交
-
-
由 Camille GILLOT 提交于
-
由 Camille GILLOT 提交于
-
由 Camille GILLOT 提交于
-
由 Camille GILLOT 提交于
-
由 Camille GILLOT 提交于
-
由 Camille GILLOT 提交于
-
- 17 7月, 2021 1 次提交
-
-
由 Richard Cobbe 提交于
Consider all fields when comparing DllImports, to remove nondetermininsm in multiple-definitions test
-
- 16 7月, 2021 2 次提交
-
-
由 Camille GILLOT 提交于
-
由 Camille GILLOT 提交于
The two paths will be modified independently in the next few commits.
-
- 15 7月, 2021 1 次提交
-
-
由 Joshua Nelson 提交于
Proc-macros are always compiled for the host, so this should be the same in every way as recompiling the crate. I am not sure why the previous code special-cased the target, since the compiler properly gives an error when trying to load a crate for a different host: ``` error[E0461]: couldn't find crate `dependency` with expected target triple x86_64-unknown-linux-gnu --> /home/joshua/rustc4/src/test/ui/cfg-dependent.rs:8:2 | LL | dependency::is_64(); | ^^^^^^^^^^ | = note: the following crate versions were found: crate `dependency`, target triple i686-unknown-linux-gnu: /home/joshua/rustc4/build/x86_64-unknown-linux-gnu/test/ui/cfg-dependent/auxiliary/libdependency.so ``` I think another possible fix is to remove the check altogether. But I'm not sure, and this fix works, so I'm not making the larger change here.
-
- 14 7月, 2021 2 次提交
-
-
由 Camille GILLOT 提交于
-
由 Camille GILLOT 提交于
-
- 11 7月, 2021 1 次提交
-
-
由 Vadim Petrochenkov 提交于
This information is already available from `ExpnData`
-
- 10 7月, 2021 2 次提交
-
-
由 Deadbeef 提交于
-
由 Richard Cobbe 提交于
-
- 07 7月, 2021 2 次提交
-
-
由 Camille GILLOT 提交于
-
由 Camille GILLOT 提交于
-
- 06 7月, 2021 1 次提交
-
- 05 7月, 2021 1 次提交
-
-
由 bjorn3 提交于
The information is stored in used_crate_source too anyway
-
- 01 7月, 2021 1 次提交
-
-
由 bjorn3 提交于
-