| Message ID | alpine.LSU.2.20.1701221055480.3033@anthias.pfeifer.com |
|---|---|
| State | New |
| Headers | show |
Hi Gerald, > Looking through README.Portability I noticed what feels like > an obsolete reference to Irix 6. Do we really support that, > or versions that feature this issue, any longer? > > Rainer, I think you may have been the last Irix contributor/ > tester we've had? > > (The last entry I could find was in gcc-4.7/buildstat.html .) right, both IRIX and Tru64 UNIX support were removed after GCC 4.7, so this can certainly go. Thanks for noticing. Rainer
On Sun, 22 Jan 2017, Rainer Orth wrote: > right, both IRIX and Tru64 UNIX support were removed after GCC 4.7, > so this can certainly go. Thanks for the quick response and confirmation, Rainer! I got a little confused since https://gcc.gnu.org/gcc-4.7/changes.html mentions deprecations, but https://gcc.gnu.org/gcc-4.8/changes.html then does not have anything on actual removals (and I wasn't sure whether IRIX 6.5 was the final version). I applied the change with the following ChangeLog: 2017-01-22 Gerald Pfeifer <gerald@pfeifer.com> * README.Portability: Remove note on an Irix compatibility issue. Gerald
Index: gcc/README.Portability =================================================================== --- gcc/README.Portability (revision 244756) +++ gcc/README.Portability (working copy) @@ -21,14 +21,6 @@ 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.