Path: utzoo!telly!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!ucsd!ucbvax!tut.cis.ohio-state.edu!allosaur.cis.ohio-state.edu!bob
From: bob@allosaur.cis.ohio-state.edu (Bob Sutterfield)
Newsgroups: gnu.gcc
Subject: Re: GCC 1.35 and X11
Message-ID: <BOB.89May22101941@allosaur.cis.ohio-state.edu>
Date: 22 May 89 14:19:41 GMT
References: <31574@sri-unix.SRI.COM> <8905201832.AA11320@xenon.lcs.mit.edu>
Sender: news@tut.cis.ohio-state.edu
Reply-To: Bob Sutterfield <bob@cis.ohio-state.edu>
Organization: The Ohio State University Dept of Computer & Information Science
Lines: 22
In-reply-to: keith@EXPO.LCS.MIT.EDU's message of 20 May 89 18:32:29 GMT

A GCC comment/status report/mild endorsement, seen in another newsgroup:

   From: keith@EXPO.LCS.MIT.EDU
   Newsgroups: comp.windows.x
   Message-ID: <8905201832.AA11320@xenon.lcs.mit.edu>
   Date: 20 May 89 18:32:29 GMT
   
   The X server on the sun should build fine with GCC 1.35; rms gave me a 
   preliminary version (1.34.92) to test before he shipped 1.35.  I compiled
   our entire core sources (R3++) -O -g -fstrength-reduce -fpcc-struct-return
   and it ran without trouble.  We are now regularly building the X server
   with GCC (as it nearly doubles the speed in monochrome) so you should 
   expect fewer troubles with the next release of X (we just need to keep
   making sure it compiles with the sun compiler as well.  Sigh).
   
   You should probably not use -finline-functions; gcc has a funny idea
   of "reasonable" inlinable functions; the sample server uses enough macros
   where needed for performance to make the speedup from -finline-functions
   negligable, while the code bloat is quite amazing.
   
   Keith Packard
   MIT X Consortium