https://gcc.gnu.org/g:fe3c79d66f49ae6756c8bfe74e6593ad04ca07ff
commit r17-1093-gfe3c79d66f49ae6756c8bfe74e6593ad04ca07ff Author: Dhruv Chawla <[email protected]> Date: Tue May 19 12:43:32 2026 +0000 alpha: Fix typos in various files Signed-off-by: Dhruv Chawla <[email protected]> gcc/ChangeLog: * config/alpha/alpha.cc (alpha_pass_by_reference): Fix typos. (alpha_reorg): Likewise. * config/alpha/predicates.md: Likewise. libgcc/ChangeLog: * config/alpha/vms-unwind.h (alpha_vms_fallback_frame_state): Fix typos. Diff: --- gcc/config/alpha/alpha.cc | 4 ++-- gcc/config/alpha/predicates.md | 2 +- libgcc/config/alpha/vms-unwind.h | 4 ++-- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/gcc/config/alpha/alpha.cc b/gcc/config/alpha/alpha.cc index f81391bdff2d..9b8433c5bb04 100644 --- a/gcc/config/alpha/alpha.cc +++ b/gcc/config/alpha/alpha.cc @@ -6415,7 +6415,7 @@ alpha_pass_by_reference (cumulative_args_t, const function_arg_info &arg) This introduces sort of ABI incompatibility, but until _Float32 was introduced, C-family languages promoted 32-bit float variable arg to - a 64-bit double, and it was not allowed to pass float as a varible + a 64-bit double, and it was not allowed to pass float as a variable argument. Passing _Complex float as a variable argument never worked on alpha. Thus, we have no backward compatibility issues to worry about, and passing unpromoted _Float32 and _Complex float @@ -10099,7 +10099,7 @@ static void alpha_reorg (void) { /* Workaround for a linker error that triggers when an exception - handler immediatelly follows a sibcall or a noreturn function. + handler immediately follows a sibcall or a noreturn function. In the sibcall case: diff --git a/gcc/config/alpha/predicates.md b/gcc/config/alpha/predicates.md index b5ff4ab6dab7..68e3ac69f2a1 100644 --- a/gcc/config/alpha/predicates.md +++ b/gcc/config/alpha/predicates.md @@ -169,7 +169,7 @@ case CONST: if (TARGET_EXPLICIT_RELOCS) { - /* We don't split symbolic operands into something unintelligable + /* We don't split symbolic operands into something unintelligible until after reload, but we do not wish non-small, non-global symbolic operands to be reconstructed from their high/lo_sum form. */ diff --git a/libgcc/config/alpha/vms-unwind.h b/libgcc/config/alpha/vms-unwind.h index 34ef0ba504ce..a1b0d455f832 100644 --- a/libgcc/config/alpha/vms-unwind.h +++ b/libgcc/config/alpha/vms-unwind.h @@ -114,13 +114,13 @@ alpha_vms_fallback_frame_state (struct _Unwind_Context *context, fs->retaddr_column = RA_COLUMN; /* If PV designates a VMS exception vector or condition handler, we need to - do as if the caller was the signaling point and estabish the state of the + do as if the caller was the signaling point and establish the state of the intermediate VMS code (CFA, RA and saved register locations) as if it was a single regular function. This requires special processing. The datastructures available from an condition dispatcher frame (signal context) do not contain the values of most callee-saved registers, so - whathever PV designates, we need to account for the registers it saves. + whatever PV designates, we need to account for the registers it saves. Besides, we need to express all the locations with respect to a consistent CFA value, so we compute this first. */
