From 5b5ea34d6f42bab11619a596f1bf84ef47e2c802 Mon Sep 17 00:00:00 2001 From: gerald Date: Sun, 22 Jan 2017 15:52:02 +0000 Subject: [PATCH] * README.Portability: Remove note on an Irix compatibility issue. git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@244759 138bc75d-0d04-0410-961f-82ee72b054a4 --- gcc/ChangeLog | 4 ++++ gcc/README.Portability | 8 -------- 2 files changed, 4 insertions(+), 8 deletions(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index f1e77e3a2e9..f1665c683b7 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,7 @@ +2017-01-22 Gerald Pfeifer + + * README.Portability: Remove note on an Irix compatibility issue. + 2017-01-22 Dimitry Andric * gcov.c (INCLUDE_ALGORITHM): Define. diff --git a/gcc/README.Portability b/gcc/README.Portability index eec3da0616f..b5a099edc0f 100644 --- 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. -- 2.11.4.GIT