Skip to content

chore: Fix typos #143315

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -78,7 +78,7 @@ pub fn generate_load_store_tests(

assert!(
used_stores.into_iter().all(|b| b),
"Not all store tests have been paired with a load. Consider generating specifc store-only tests"
"Not all store tests have been paired with a load. Consider generating specific store-only tests"
);

let preamble =
Expand Down Expand Up @@ -119,7 +119,7 @@ pub fn generate_load_store_tests(
/// let loaded == load_intrinsic([true_predicate], storage.as_ptr())
/// assert!(loaded == data);
/// ```
/// We intialise our data such that the value stored matches the index it's stored to.
/// We initialise our data such that the value stored matches the index it's stored to.
/// By doing this we can validate scatters by checking that each value in the storage
/// array is either 0 or the same as its index.
fn generate_single_test(
Expand Down
2 changes: 1 addition & 1 deletion library/stdarch/crates/stdarch-verify/tests/arm.rs
Original file line number Diff line number Diff line change
Expand Up @@ -503,7 +503,7 @@ fn matches(rust: &Function, arm: &Intrinsic) -> Result<(), String> {
// TODO: This instruction checking logic needs work to handle multiple instructions and to only
// look at aarch64 insructions.
// The ACLE's listed instructions are a guideline only and compilers have the freedom to use
// different instructions in dfferent cases which makes this an unreliable testing method. It
// different instructions in different cases which makes this an unreliable testing method. It
// is of questionable value given the intrinsic test tool.
{
for instr in rust.instrs {
Expand Down
Loading