Pushed.
Gerald
gcc:
* doc/extend.texi (Integer Overflow Builtins): Spell compile time
without dash when a noun.
* doc/invoke.texi (Warning Options): Ditto.
* doc/passes.texi (Tree SSA passes): Ditto.
* doc/rtl.texi (Conversions): Ditto.
---
gcc/doc/extend.texi | 2 +-
gcc/doc/invoke.texi | 2 +-
gcc/doc/passes.texi | 2 +-
gcc/doc/rtl.texi | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
index ad2eb95eb54..4d57c003dc4 100644
--- a/gcc/doc/extend.texi
+++ b/gcc/doc/extend.texi
@@ -16330,7 +16330,7 @@ precision and signedness of the given bit-field, rather
than precision and signe
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.
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 42379329bf8..76fae1da0bb 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -7405,7 +7405,7 @@ requires an unsigned argument and the argument is signed
and vice versa.
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
diff --git a/gcc/doc/passes.texi b/gcc/doc/passes.texi
index f8e6c7c71a9..a5bbbbcd97e 100644
--- a/gcc/doc/passes.texi
+++ b/gcc/doc/passes.texi
@@ -796,7 +796,7 @@ pass is located in @code{tree-nrv.cc} and is described by
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
diff --git a/gcc/doc/rtl.texi b/gcc/doc/rtl.texi
index 6cf6a6ef4b4..f606b97389f 100644
--- a/gcc/doc/rtl.texi
+++ b/gcc/doc/rtl.texi
@@ -2996,7 +2996,7 @@ to do it.
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
--
2.54.0
