rust/tests/ui/no_std, branch try-perfhttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=try-perf2025-07-01T10:16:56+00:00cleaned up some tests2025-07-01T10:16:56+00:00KivooeoKivooeo123@gmail.com2025-06-29T19:05:58+00:00urn:sha1:da5c6395dad7c5be33f842c3660ae2f6af287f3amoved tests2025-06-29T19:03:28+00:00KivooeoKivooeo123@gmail.com2025-06-29T19:03:28+00:00urn:sha1:4feb5de34c1e41da0c10e149e243a25a6eafcd17Fix a bunch of missing unwinder related definitions2025-06-24T09:06:49+00:00bjorn317426603+bjorn3@users.noreply.github.com2025-06-24T09:04:36+00:00urn:sha1:659da5843bd0c176c47ca190d2b1cfaa690ffa09
cg_llvm likely just optimizes out their references for these tests, but
cg_clif doesn't and would thus give a linker error.
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.
Rollup merge of #138904 - madsmtm:apple-test-no-std, r=tgross352025-04-11T03:31:45+00:00Stuart CookZalathar@users.noreply.github.com2025-04-11T03:31:45+00:00urn:sha1:9a9a0781fa219b7c4d04808a8583c053fa8b12ed
Test linking and running `no_std` binaries
I looked around, but it seems that we do not have a test that tests a `#![no_std]` + `#![no_main]` binary. So now I've added one. Motivated by discussion in [this Zulip thread](https://rust-lang.zulipchat.com/#narrow/channel/219381-t-libs/topic/Provide.20.60__isPlatformVersionAtLeast.60.20in.20.60std.60.3F/with/507870028).
r? ```@tgross35```
try-job: arm-android
try-job: armhf-gnu
try-job: dist-ohos
try-job: x86_64-mingw-1
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:4d649906900cd833b0680f53b8c197b087711a4aTest linking and running no_std binaries2025-03-24T22:22:08+00:00Mads Marquartmads@marquart.dk2025-03-24T20:55:14+00:00urn:sha1:f9770e742ad3853d2a472e422b00cdbe8578faae[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives2024-02-16T20:02:50+00:00许杰友 Jieyou Xu (Joe)jieyouxu@outlook.com2024-02-16T20:02:50+00:00urn:sha1:ec2cc761bc7067712ecc7734502f703fe3b024c8Stop mentioning internal lang items in no_std binary errors2024-01-10T20:18:54+00:00Nilstrieb48135649+Nilstrieb@users.noreply.github.com2023-10-02T12:32:31+00:00urn:sha1:da26317a8a69fed3f7b96457c643121e75954933
When writing a no_std binary, you'll be greeted with nonsensical errors
mentioning lang items like eh_personality and start. That's pretty bad
because it makes you think that you need to define them somewhere! But
oh no, now you're getting the `internal_features` lint telling you that
you shouldn't use them! But you need a no_std binary! What now?
No problem! Writing a no_std binary is super easy. Just use panic=abort
and supply your own platform specific entrypoint symbol (like `main`)
and you're good to go. Would be nice if the compiler told you that,
right?
This makes it so that it does do that.