Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!peyote!woan
From: woan@peyote.cactus.org (Ronald S. Woan)
Newsgroups: comp.unix.aix
Subject: Re: GCC and G++ for RS/6000 ?
Summary: Could you post some examples
Keywords: g++, gcc RS/6000
Message-ID: <1866@peyote.cactus.org>
Date: 6 Aug 90 03:27:58 GMT
References: <176@hafro.is> <1990Aug4.225222.27970@m2xenix.psg.com>
Organization: Capital Area Central Texas Unix Society, Austin, TX
Lines: 33

In article <1990Aug4.225222.27970@m2xenix.psg.com>, steven@m2xenix.psg.com (Steven Furber) writes:
> From what conversations I have had with the local IBM RS/6000 SE's, GNU
> products are not going to be ported or supported by IBM; EMACS was
> dropped because of the current lawsuit that is going on.

I think it would be better termed as a potential lawsuit by Unipress.

> Something that I pointed out to the SE who was at work last week was
> that the XLC compiler seems to choke on a lot of "standard" C code,
> making easy ports that work on other *NIX platforms a pain.  When he
> asked what I saw as a solution I suggestd GCC, since it would open up
> the doors to the rest of the GNU universe and the code written thereof.
> Since there is (from my understadning) no money that IBM can make off of
> a port, the SE doesn't see where IBM would get into it-- even if the
> lawsuit is settled.

I hate it when people say things like this without backing it up. Could you
post some examples of the "standard" (I take it this means K&R) C code 
that xlc chokes on? I have a feeling it is mainly due to a lack of
understanding of the header standards (did you look at the BSD porting
document in /usr/lpp/bos?). GCC would be nice, but then you would loose all
of the optimizations performed by xlc (very significant from recent
comp.arch postings) that cannot be handled by gcc in its current form. GCC
is great for 680?0 code but it leaves much to be desired for the current
generation of RISC processors, especially the IBM one.

					Ron

-- 
+-----All Views Expressed Are My Own And Are Not Necessarily Shared By------+
+------------------------------My Employer----------------------------------+
+ Ronald S. Woan                                     woan@peyote.cactus.org +
+ If nothing else works                              woan@soda.berkeley.edu +