Ok to commit?

When eyeballing the r12-440 / bd1cd0d0e0fe / "Remove
CC0" commit, I noticed parts that could be improved.

Regarding the first change: at first I thought that just
removing the word "better" was the best choice, as the
compared part (cc0) was apparently removed, but the
paragraph after the one in the patch (still) does speak of
"implicit setting" (i.e. cc0-style), but now as hypothetical
reasoning.  So, just add that to clarify what is not-better.

The second change is just that there's no non-modern
representation, so the "Modern" qualifier is just confusing.

gcc:
        * doc/tm.texi.in (Condition Code): Tweak post-cc0 wording.
        * doc/tm.texi: Regenerate.
---
 gcc/doc/tm.texi    | 4 ++--
 gcc/doc/tm.texi.in | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/gcc/doc/tm.texi.in b/gcc/doc/tm.texi.in
index d8e3de14af1a..9009eaecc4de 100644
--- a/gcc/doc/tm.texi.in
+++ b/gcc/doc/tm.texi.in
@@ -4269,7 +4269,7 @@ or @code{TARGET_MAX_ANCHOR_OFFSET} is set to a nonzero 
value.
 @cindex condition code status
 
 Condition codes in GCC are represented as registers,
-which provides better schedulability for
+which provides better schedulability than implicit clobbering for
 architectures that do have a condition code register, but on which
 most instructions do not affect it.  The latter category includes
 most RISC machines.
@@ -4300,7 +4300,7 @@ specified already in the compare instruction.  In this 
case, you are not
 interested in most macros in this section.
 
 @menu
-* MODE_CC Condition Codes::  Modern representation of condition codes.
+* MODE_CC Condition Codes::  Representation of condition codes.
 @end menu
 
 @node MODE_CC Condition Codes
-- 
2.11.0

brgds, H-P

Reply via email to