rust/tests/ui/print-request, branch perf-tmphttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=perf-tmp2025-09-12T18:53:28+00:00Add --print target-spec-json-schema2025-09-12T18:53:28+00:00Noratrieb48135649+Noratrieb@users.noreply.github.com2025-07-26T10:39:31+00:00urn:sha1:f157ce994ea45e9faea9eff89c5f8b3d4ea77b6e
This schema is helpful for people writing custom target spec JSON. It
can provide autocomplete in the editor, and also serves as documentation
when there are documentation comments on the structs, as `schemars` will
put them in the schema.
tests: Skip supported-crate-types test on musl hosts2025-07-18T17:05:32+00:00Jens Reideladrian@travitia.xyz2025-07-18T16:33:26+00:00urn:sha1:d1a146bbbbe2de47b77aacf3cb47eb79eb39338b
This test depends on the target-specific behavior of crt-static for musl
targets. However, running the testsuite on a musl host requires
setting `crt-static` to `false`, as it wouldn't otherwise be possible to
build rustc. This in turn will enable `-Ctarget-feature=-crt-static` for
all tests, mismatching the expected `+crt-static` for the musl target
tested in this testcase.
Since this test specifically tests the default value of `crt-static` for
the musl target, ignoring it entirely makes more sense than manually
setting `-Ctarget-feature=+crt-static` here, but both would be valid
approaches.
Signed-off-by: Jens Reidel <adrian@travitia.xyz>
cleaned up some tests2025-07-04T19:45:24+00:00KivooeoKivooeo123@gmail.com2025-07-01T13:24:12+00:00urn:sha1:b28806da237176468ab2afae42b51fe43ad416e6moved tests2025-07-01T13:21:05+00:00KivooeoKivooeo123@gmail.com2025-07-01T13:21:05+00:00urn:sha1:986f1c9b692665d4e7388062b8d8536acb0c99fdRevert overeager warning for misuse of `--print native-static-libs`2025-06-16T19:43:36+00:00Jubilee Youngworkingjubilee@gmail.com2025-06-16T19:07:24+00:00urn:sha1:7b29a5d2827f4336ee2c3ca163378c9dc5a82238
In a PR to emit warnings on misuse of `--print native-static-libs`,
we did not consider the matter of composing parts of build systems.
If you are not directly invoking rustc, it can be difficult to know
when you will in fact compile a staticlib, so making sure everyone
uses `--print native-static-lib` correctly can be just a nuisance.
This reverts the following commits:
- f66787a08d57dc1296619b314d2be596085bfeef
- 72a9219e82c157041bfc8dfd378c9cb2b09c0650
- 98bb597c05c32365abbd6898f278b097352774ed
- c59b70841c36277464b51161e3fcf12dfcb667e0
Next cycle we can reland a slightly more narrowly focused variant or one
that focuses on `--emit` instead of `--print native-static-libs`.
But in its current state, I am not sure the warning is very useful.
check all crate-type to find staticlib2025-05-02T14:57:14+00:00xizheyinxizheyin@smail.nju.edu.cn2025-05-02T14:56:27+00:00urn:sha1:72a9219e82c157041bfc8dfd378c9cb2b09c0650
Signed-off-by: xizheyin <xizheyin@smail.nju.edu.cn>
Emit warning while outputs is not exe and prints linkage info2025-05-02T14:08:58+00:00xizheyinxizheyin@smail.nju.edu.cn2025-03-07T02:13:30+00:00urn:sha1:c59b70841c36277464b51161e3fcf12dfcb667e0
Signed-off-by: xizheyin <xizheyin@smail.nju.edu.cn>
UI tests: migrate remaining compile time `error-pattern`s to line annotations2025-04-13T18:48:53+00:00Vadim Petrochenkovvadim.petrochenkov@gmail.com2025-04-12T19:40:34+00:00urn:sha1:93bee0789a45ea7d5d65bb9301c4ad5ece3abeb2
when possible.
Fix up tests on wasm and msvc, and rebase conflicts2025-04-03T08:08:55+00:00Vadim Petrochenkovvadim.petrochenkov@gmail.com2025-04-02T15:13:53+00:00urn:sha1:4916d44b59a2b5347506b4551b389fe902bdf54b
Can be fixed properly later by adding a new flag for non-exhaustive line annotation checking
compiletest: Require `//~` annotations even if `error-pattern` is specified2025-04-03T08:08:55+00:00Vadim Petrochenkovvadim.petrochenkov@gmail.com2025-03-28T23:41:32+00:00urn:sha1:4d649906900cd833b0680f53b8c197b087711a4a