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
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:
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. */
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. */