Update copyright years.

[thirdparty/gcc.git] / gcc / README.Portability

diff --git a/gcc/README.Portability b/gcc/README.Portability
index 4101a2f7b4240e998f83f5bd61583b6c92b33cac..cd03da7216008b8ca8e2149b2d22dd96007d7b7d 100644 (file)
--- a/gcc/README.Portability
+++ b/gcc/README.Portability
@@ -1,4 +1,4 @@
-Copyright (C) 2000, 2003 Free Software Foundation, Inc.
+Copyright (C) 2000-2022 Free Software Foundation, Inc.
 
 This file is intended to contain a few notes about writing C code
 within GCC so that it compiles without error on the full range of
@@ -6,7 +6,7 @@ compilers GCC needs to be able to compile on.
 
 The problem is that many ISO-standard constructs are not accepted by
 either old or buggy compilers, and we keep getting bitten by them.
-This knowledge until know has been sparsely spread around, so I
+This knowledge until now has been sparsely spread around, so I
 thought I'd collect it in one useful place.  Please add and correct
 any problems as you come across them.
 
@@ -21,14 +21,6 @@ http://gcc.gnu.org/codingconventions.html
 String literals
 ---------------
 
-Irix6 "cc -n32" and OSF4 "cc" have problems with constant string
-initializers with parens around it, e.g.
-
-const char string[] = ("A string");
-
-This is unfortunate since this is what the GNU gettext macro N_
-produces.  You need to find a different way to code it.
-
 Some compilers like MSVC++ have fairly low limits on the maximum
 length of a string literal; 509 is the lowest we've come across.  You
 may need to break up a long printf statement into many smaller ones.