This is the mail archive of the
cygwin-xfree@sourceware.cygnus.com
mailing list for the Cygwin project.
RE: Xggi/glide
- To: "Mumit Khan" <khan@xraylith.wisc.edu>
- Subject: RE: Xggi/glide
- From: "Suhaib M. Siddiqi" <ssiddiqi@inspirepharm.com>
- Date: Sun, 11 Jul 1999 20:52:23 -0400
- Cc: "Cygwin-Xfree@Sourceware.Cygnus.Com" <cygwin-xfree@sourceware.cygnus.com>
Ummm, with any optimization it did work. i tool all the flags -ansi,
-pedantic and blah blah out, and it compiled.
By the way, the tele module in /degas/lib/libggi/display/tele was doing the
same
thing, always. I could never figure out what was going on, so I started
disableing (i.e --disable-tele) module compilation. I had this problem
with anothe X11/MOTIF application which I was trying to port from SGI. and I
kept getting
this b0 crashes of assembler. This weekend when i took some of the
uneccessary socket
stuff out from X11lib then X11 compilation also gave this error. That is
when i though
i should check with gcc Pro to see what this crash of assembler with b0
error means, which
have seen a few times.
Suhaib
> -----Original Message-----
> From: Mumit Khan [mailto:khan@xraylith.wisc.edu]
> Sent: Sunday, July 11, 1999 8:18 PM
> To: Suhaib M. Siddiqi
> Subject: RE: Xggi/glide
>
>
> On Sun, 11 Jul 1999, Suhaib M. Siddiqi wrote:
>
> >
> > Mumit,
> > It is still doing assembler crash.
> > I am using
> > bash-2.02$
> > gcc -c -save-temps -c -O2 -ansi -pedantic -I../.. -I../../exports/in
> > clude -D__i386__ -DX_LOCALE -D_MT -DNO_TCP_H -DFUNCPROTO=15
> -DNARROWPROTO -D
> > _XL
> > IBINT_ -I../../lib/xtrans -DTCPCONN -DHAS_STICKY_DIR_BIT
> -DX11_t -DTRANS_CL
> > IEN
> > T x11trans.c
> > ../../lib/xtrans/Xtrans.c: In function `_X11TransSelectTransport':
> > In file included from x11trans.c:91:
> > ../../lib/xtrans/Xtrans.c:185: warning: ANSI C forbids
> braced-groups within
> > expr
> > essions
> > x11trans.s: Assembler messages:
> > x11trans.s:814: Error: bad register name `b0'
> > bash-2.02$
> >
>
> Got it. You've found a genuine bug in all versions of gcc, including the
> upcoming gcc-2.95. I'll see if I can find a cure sometime soon.
>
> In the meantime, your only hope is to compile that one file without
> optimization (ie., no -O<x> option).
>
> Regards,
> Mumit
>
>