[gcc r12-7639] Spelling fix - cannott -> cannot [PR104899]

[gcc r12-7639] Spelling fix - cannott -> cannot [PR104899]

[Jakub Jelinek]

https://gcc.gnu.org/g:b42446716607992655e967fddc36a672e52fe156

commit r12-7639-gb42446716607992655e967fddc36a672e52fe156
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Mon Mar 14 10:40:47 2022 +0100

    Spelling fix - cannott -> cannot [PR104899]
    
    This fixes typos and while changing that, also uses %< %> around attribute
    names and fixes up formatting.
    
    2022-03-14  Jakub Jelinek  <jakub@redhat.com>
    
            PR other/104899
            * config/bfin/bfin.cc (bfin_handle_longcall_attribute): Fix a typo
            in diagnostic message - cannott -> cannot.  Use %< and %> around
            names of attribute.  Avoid too long line.
            * range-op.cc (operator_logical_and::op1_range): Fix up a typo
            in comment - cannott -> cannot.  Use 2 spaces after . instead of one.

Diff:
---
 gcc/config/bfin/bfin.cc | 3 ++-
 gcc/range-op.cc         | 2 +-
 2 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/gcc/config/bfin/bfin.cc b/gcc/config/bfin/bfin.cc
index c749b4894d7..b2a9142f5f9 100644
--- a/gcc/config/bfin/bfin.cc
+++ b/gcc/config/bfin/bfin.cc
@@ -4763,7 +4763,8 @@ bfin_handle_longcall_attribute (tree *node, tree name,
 	  && lookup_attribute ("longcall", TYPE_ATTRIBUTES (*node))))
     {
       warning (OPT_Wattributes,
-	       "cannott apply both longcall and shortcall attributes to the same function");
+	       "cannot apply both %<longcall%> and %<shortcall%> attributes "
+	       "to the same function");
       *no_add_attrs = true;
     }
 
diff --git a/gcc/range-op.cc b/gcc/range-op.cc
index ebc21d6038a..464a1f839fd 100644
--- a/gcc/range-op.cc
+++ b/gcc/range-op.cc
@@ -2532,7 +2532,7 @@ operator_logical_and::op1_range (irange &r, tree type,
        break;
      default:
        // Any other result means only one side has to be false, the
-       // other side can be anything. So we cannott be sure of any
+       // other side can be anything.  So we cannot be sure of any
        // result here.
        r = range_true_and_false (type);
        break;