correct comments

This commit is contained in:
Oneirical 2024-05-08 21:44:57 -04:00
parent 79cf61a9ae
commit 304c183d4f
16 changed files with 19 additions and 16 deletions

View File

@ -1,4 +1,4 @@
# This test verifies that the Rust compiler can still compile correctly when the unstable no_global_oom_handling feature is turned on, which disables global error handling in alloc.
# This test checks that alloc can still compile correctly when the unstable no_global_oom_handling feature is turned on.
# See https://github.com/rust-lang/rust/pull/84266
include ../tools.mk

View File

@ -1,4 +1,4 @@
# This test verifies that the Rust compiler can still compile correctly when the unstable no_rc feature is turned on, which disables rc in alloc.
# This test checks that alloc can still compile correctly when the unstable no_rc feature is turned on.
# See https://github.com/rust-lang/rust/pull/89891
include ../tools.mk

View File

@ -1,4 +1,4 @@
# This test verifies that the Rust compiler can still compile correctly when the unstable no_sync feature is turned on, which disables sync in alloc.
# This test checks that alloc can still compile correctly when the unstable no_sync feature is turned on.
# See https://github.com/rust-lang/rust/pull/89891
include ../tools.mk

View File

@ -1,4 +1,6 @@
# This test intentionally creates a circular dependency, and checks if this causes the resurgence of the compiler bug linked below.
# This test is designed to intentionally introduce a circular dependency scenario to check that a specific compiler bug doesn't make a resurgence.
# The bug in question arose when at least one crate required a global allocator, and that crate was placed after the one defining it in the linker order.
# The generated symbols.o should not result in any linker errors.
# See https://github.com/rust-lang/rust/issues/112715
# ignore-cross-compile

View File

@ -1,4 +1,5 @@
# This test reads two object archives with the same filename, and extracts each one to a unique location. This checks that the functionality of the linked PR is preserved.
# When two object archives with the same filename are present, an iterator is supposed to inspect each object, recognize the duplication and extract each one to a different directory.
# This test checks that this duplicate handling behaviour has not been broken.
# See https://github.com/rust-lang/rust/pull/24439
# ignore-cross-compile

View File

@ -1,4 +1,4 @@
# This test verifies that dynamic Rust linking with C does not encounter any errors, with dynamic dependencies given preference over static.
# This test checks that dynamic Rust linking with C does not encounter any errors, with dynamic dependencies given preference over static.
# See https://github.com/rust-lang/rust/issues/10434
# ignore-cross-compile

View File

@ -1,4 +1,4 @@
# This test verifies that dynamic Rust linking with C does not encounter any errors, with static dependencies given preference over dynamic. (This is the default behaviour.)
# This test checks that dynamic Rust linking with C does not encounter any errors, with static dependencies given preference over dynamic. (This is the default behaviour.)
# See https://github.com/rust-lang/rust/issues/10434
# ignore-cross-compile

View File

@ -1,4 +1,4 @@
# This test verifies that C linking with Rust does not encounter any errors, with dynamic libraries.
# This test checks that C linking with Rust does not encounter any errors, with dynamic libraries.
# See https://github.com/rust-lang/rust/issues/10434
# ignore-cross-compile

View File

@ -1,4 +1,4 @@
# This test verifies that C linking with Rust does not encounter any errors, with static libraries.
# This test checks that C linking with Rust does not encounter any errors, with static libraries.
# See https://github.com/rust-lang/rust/issues/10434
# ignore-cross-compile

View File

@ -1,4 +1,4 @@
# This test verifies that static Rust linking with C does not encounter any errors, with dynamic dependencies given preference over static.
# This test checks that static Rust linking with C does not encounter any errors, with dynamic dependencies given preference over static.
# See https://github.com/rust-lang/rust/issues/10434
# ignore-cross-compile

View File

@ -1,4 +1,4 @@
# This test verifies that static Rust linking with C does not encounter any errors, with static dependencies given preference over dynamic. (This is the default behaviour.)
# This test checks that static Rust linking with C does not encounter any errors, with static dependencies given preference over dynamic. (This is the default behaviour.)
# See https://github.com/rust-lang/rust/issues/10434
# ignore-cross-compile

View File

@ -1,4 +1,4 @@
# This test verifies that cdylibs can link against dylibs as dependencies, after this restriction was disabled.
# This test checks that cdylibs can link against dylibs as dependencies, after this restriction was disabled.
# See https://github.com/rust-lang/rust/commit/72aaa3a414d17aa0c4f19feafa5bab5f84b60e63
# ignore-cross-compile

View File

@ -1,4 +1,4 @@
# When the cdylib crate type was added as a variation of dylib, it needed a test to verify its function.
# When the cdylib crate type was added as a variation of dylib, it needed a test to check its function.
# See https://github.com/rust-lang/rust/pull/33553
# ignore-cross-compile

View File

@ -1,4 +1,4 @@
# This test intentionally feeds invalid inputs to codegen and checks if the error message outputs contain the expected strings.
# This test intentionally feeds invalid inputs to codegen and checks if the error message outputs contain specific helpful indications.
# ignore-cross-compile
include ../tools.mk

View File

@ -1,4 +1,4 @@
# When provided standard input piped directly into rustc, this test verifies that the compilation completes successfully and that the output can be executed.
# When provided standard input piped directly into rustc, this test checks that the compilation completes successfully and that the output can be executed.
# See https://github.com/rust-lang/rust/pull/28805
# ignore-cross-compile

View File

@ -1,4 +1,4 @@
# This test verifies that extern crate declarations in Cargo without a corresponding declaration in the manifest of a dependency are NOT allowed.
# This test checks that extern crate declarations in Cargo without a corresponding declaration in the manifest of a dependency are NOT allowed.
# See https://github.com/rust-lang/rust/pull/21113
include ../tools.mk