🚀 go-pugleaf

> Date: Fri, 10 Apr 92 17:55:39 +1000
> From: charles@probitas.cs.utas.edu.au (Charles Lakos)
> Message-Id: <9204100755.AA41189@probitas.cs.utas.edu.au>
> Newsgroups: gnu.gcc.bug
> References: <9204080723.AA01056@cygnus.com>

> Mike, sorry for latching onto one of your replies to an unrelated question
> in the news, but I was wondering if you could answer a couple of simple
> questions about getting Interviews up under gcc-2.1.

> 1. Are the problems likely to be removed with further releases of gcc or
>    will a set of diffs be required as before?

Your question is so imprecise as to make it hard to answer.  I do not
make releases of ``official'' InterViews so I cannot say that patches
to InterViews will not be necessary.  As to patches to gcc, the goal
is to have gcc (g++) accept all the necessary parts of ARM to allow
complete compilation of InterViews.

Future releases of gcc will probably be able to work with InterViews.

> 2. Are you working on such a set of diffs, and if so when might they be ready?

I work on the main g++ tree.  I don't do diffs, as a general rule.
(Anymore) I have had diffs for a very long time, so I guess the answer
to your question is, now.  See pub/contrib/g++ on
interviews.stanford.edu for details.

> 3. Having looked through your earlier diffs, the significant differences 
>    seemed to be the types of parameters in the library calls.  Are these 
>    likely to be the the main problems now?

No, not really.

> 4. Is it just coincidence that the InterViews samples using Unidraw do not
>    work under gcc-2.1?

I would claim that idraw uses Unidraw, and I would claim that idraw
works, so I would further claim that the above it not a true
statement.

> BTW, I am trying to get the stuff to work on a Sun Sparcstation.

Should work semi ok.  ibuild and doc are loses probably right now.  If
you go with my patch kit, ibuild will work.