of the underlying type.
For example, the following macro can be used to portably check, at
-compile-time, whether or not adding two constant integers will overflow,
+compile time, whether or not adding two constant integers will overflow,
and perform the addition only when it is known to be safe and not to trigger
a @option{-Woverflow} warning.
Warn about calls to formatted input/output functions such as @code{snprintf}
and @code{vsnprintf} that might result in output truncation. When the exact
number of bytes written by a format directive cannot be determined at
-compile-time it is estimated based on heuristics that depend on
+compile time it is estimated based on heuristics that depend on
the @var{level} argument and on optimization. While enabling optimization
will in most cases improve the accuracy of the warning, it may also result
in false positives. Except as noted otherwise, the option uses the same
This is a propagation pass similar to CCP that tries to remove calls to
@code{__builtin_object_size} when the upper or lower bound for the size
-of the object can be computed at compile-time. It also tries to replace
+of the object can be computed at compile time. It also tries to replace
calls to @code{__builtin_dynamic_object_size} with an expression that
evaluates the upper or lower bound for the size of the object. This
pass is located in @file{tree-object-size.cc} and is described by
For all conversion operations, @var{x} must not be @code{VOIDmode}
because the mode in which to do the conversion would not be known.
-The conversion must either be done at compile-time or @var{x}
+The conversion must either be done at compile time or @var{x}
must be placed into a register.
@table @code