as the faulting instruction address in the corresponding signal context
pushed by the kernel. Leaving this address untouched may loose, because if
the triggering instruction happens to be the very first of a region, the
- later adjustements performed by the unwinder would yield an address outside
+ later adjustments performed by the unwinder would yield an address outside
that region. We need to compensate for those adjustments at some point,
which we currently do in the GCC unwinding fallback macro.
/* Define macro symbols for the VMS conditions that become Ada exceptions.
Most of these are also defined in the header file ssdef.h which has not
- yet been converted to be recoginized by Gnu C. */
+ yet been converted to be recognized by Gnu C. */
/* Defining these as macros, as opposed to external addresses, allows
them to be used in a case statement (below */
extern int MTH$_FLOOVEMAT; /* Some ACVC_21 CXA tests */
/* These codes are non standard, which is to say the author is
- not sure if they are defined in the standar message libraries
+ not sure if they are defined in the standard message libraries
so keep them as macros for now. */
#define RDB$_STREAM_EOF 20480426
#define FDL$_UNPRIKW 11829410
??? This is not a perfect solution to deal with the possible
interactions between the GNAT and the DECAda exception handling
models and better (more general) schemes are studied. This is so
- just provided as a conveniency workaround in the meantime, and
+ just provided as a convenient workaround in the meantime, and
should be use with caution since the implementation has been kept
very simple. */
asm ("mtfsb0 26");
#endif
- /* Similarily for sparc64. Achieved by masking bits in the Trap Enable Mask
+ /* Similarly for sparc64. Achieved by masking bits in the Trap Enable Mask
field of the Floating-point Status Register (see the Sparc Architecture
Manual Version 9, p 48). */
#if defined (sparc64)
constructor fashion, typically triggered by the VxWorks loader. This is
achieved by way of a special variable declaration in the crt object, the
name of which has been deduced by analyzing the output of the "munching"
- step documented for C++. The de-registration is handled symetrically,
+ step documented for C++. The de-registration is handled symmetrically,
a-la C++ destructor fashion and typically triggered by the dynamic
unloader. Note that since the tables shall be registered against a
common datastructure, libgcc should be one of the modules (vs beeing