about summary refs log tree commit diff
path: root/tests/assembly/stack-protector/stack-protector-target-support.rs
AgeCommit message (Collapse)AuthorLines
2025-07-22Rename `tests/assembly` into `tests/assembly-llvm`Guillaume Gomez-281/+0
2025-03-03Remove i586-pc-windows-msvcNoratrieb-5/+1
See MCP 840. I left a specialized error message that should help users that hit this in the wild (for example, because they use it in their CI).
2025-02-24tests: use minicore moreDavid Wood-4/+3
minicore makes it much easier to add new language items to all of the existing `no_core` tests.
2024-03-11Rename `wasm32-wasi-preview1-threads` to `wasm32-wasip1-threads`Alex Crichton-2/+1
This commit renames the current `wasm32-wasi-preview1-threads` target to `wasm32-wasip1-threads`. The need for this rename is a bit unfortunate as the previous name was chosen in an attempt to be future-compatible with other WASI targets. Originally this target was proposed to be `wasm32-wasi-threads`, and that's what was originally implemented in wasi-sdk as well. After discussion though and with the plans for the upcoming component-model target (now named `wasm32-wasip2`) the "preview1" naming was chosen for the threads-based target. The WASI subgroup later decided that it was time to drop the "preview" terminology and recommends "pX" instead, hence previous PRs to add `wasm32-wasip2` and rename `wasm32-wasi` to `wasm32-wasip1`. So, with all that history, the "proper name" for this target is different than its current name, so one way or another a rename is required. This PR proposes renaming this target cold-turkey, unlike `wasm32-wasi` which is having a long transition period to change its name. The threads-based target is predicted to see only a fraction of the traffic of `wasm32-wasi` due to the unstable nature of the WASI threads proposal itself. While I was here I updated the in-tree documentation in the target spec file itself as most of the documentation was copied from the original WASI target and wasn't as applicable to this target. Also, as an aside, I can at least try to apologize for all the naming confusion here, but this is hopefully the last WASI-related rename.
2024-03-02Add a new `wasm32-wasip1` target to rustcAlex Crichton-1/+1
This commit adds a new target called `wasm32-wasip1` to rustc. This new target is explained in these two MCPs: * https://github.com/rust-lang/compiler-team/issues/607 * https://github.com/rust-lang/compiler-team/issues/695 In short, the previous `wasm32-wasi` target is going to be renamed to `wasm32-wasip1` to better live alongside the [new `wasm32-wasip2` target](https://github.com/rust-lang/rust/pull/119616). This new target is added alongside the `wasm32-wasi` target and has the exact same definition as the previous target. This PR is effectively a rename of `wasm32-wasi` to `wasm32-wasip1`. Note, however, that as explained in rust-lang/compiler-team#695 the previous `wasm32-wasi` target is not being removed at this time. This change will reach stable Rust before even a warning about the rename will be printed. At this time this change is just the start where a new target is introduced and users can start migrating if they support only Nightly for example.
2024-02-22[AUTO_GENERATED] Migrate compiletest to use `ui_test`-style `//@` directives许杰友 Jieyou Xu (Joe)-175/+175
2024-02-22Fix tests/assembly/stack-protector/stack-protector-target-support.rs许杰友 Jieyou Xu (Joe)-1/+2
Previously the test seems to not actually test redox.
2023-11-20Remove now deprecated target x86_64-sun-solaris.Petr Sumbera-1/+1
2023-10-28Remove asmjs from testsJubilee Young-3/+2
2023-07-29Add wasm32-wasi-threads target + WASI threadsGeorgii Rylov-12/+14
2023-01-11Move /src/test to /testsAlbert Larsan-0/+285