* README.Portability: Remove note on an Irix compatibility issue.

From-SVN: r244759

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index f1e77e3a2e9b9a8cf05a977392fd1619f49bb627..f1665c683b7b4535303f4bca1d42ebd6711ce326 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,7 @@
+2017-01-22  Gerald Pfeifer  <gerald@pfeifer.com>
+
+       * README.Portability: Remove note on an Irix compatibility issue.
+
 2017-01-22  Dimitry Andric <dim@FreeBSD.org>
 
        * gcov.c (INCLUDE_ALGORITHM): Define.

diff --git a/gcc/README.Portability b/gcc/README.Portability
index eec3da0616f1331ad96733763c4fb2b4486b26ef..b5a099edc0f587d288f63f0198c0cb84759144c5 100644 (file)
--- a/gcc/README.Portability
+++ b/gcc/README.Portability
@@ -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.