Date: Wed, 8 Apr 1998 00:30:01 -0700 (PDT) From: Donn Miller <dmm125@bellatlantic.net> To: freebsd-bugs Subject: Re: gnu/6244: Lots of parse errors with gcc in 2.2.6-RELEASE Message-ID: <199804080730.AAA07767@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR gnu/6244; it has been noted by GNATS. From: Donn Miller <dmm125@bellatlantic.net> To: freebsd-gnats-submit@freebsd.org, dmm125@bellatlantic.net Cc: Subject: Re: gnu/6244: Lots of parse errors with gcc in 2.2.6-RELEASE Date: Wed, 08 Apr 1998 03:23:19 +0000 > Problem Report gnu/6244 > > Lots of parse errors with gcc in 2.2.6-RELEASE > > Confidential > no > Severity > critical > Priority > medium > Responsible > freebsd-bugs@freebsd.org > State > open > Class > sw-bug > Submitter-Id > current-users > Arrival-Date > Tue Apr 7 15:50:01 PDT 1998 > Last-Modified > Tue Apr 7 17:30:00 PDT 1998 > Originator > Donn M. Miller dmm125@bellatlantic.net > Release > 2.2.6-RELEASE > Environment > > FreeBSD myname.my.domain 2.2.6-RELEASE FreeBSD 2.2.6-RELEASE #0: > Sat Apr 4 00:42:22 GMT 1998 root@myname.my.domain:/usr/src/sys/compile/CUSTOM i386 > > Description > > gcc version 2.7.2.1 > > I've been getting ``parse errors'' a lot with 2.2.6-RELEASE, most lately when > building world. Here is a sample of a recent make world: > > In file included from /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/genextract.c:24: > /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/rtl.h:756: > parse error before `emit_jump_insn_before' > /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/rtl.h:756: warning: data definition has no type or storage class > *** Error code 1 > extern void emit_queue PROTO((void)); > extern rtx emit_move_insn PROTO((rtx, rtx)); > extern rtx emit_insn_before PROTO((rtx, rtx)); > extern rtx emit_jump_insn_before PROTO((rtx, rtx)); /* line 756 rtl.h */ > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > Where the ``parse error'' is located. > extern rtx emit_call_insn_before PROTO((rtx, rtx)); > > Also, I've gotten parse errors while building world of XFree86 3.3.2, > and also wine980330 (the last wine release in march) but in each case, > I checked the syntax and couldn't find any errors. > > How-To-Repeat > > Install 2.2.6-RELEASE. cd /usr/src && make world and note if there > are any parse errors that are unwarranted. Also try build the last wine > release in march (not the port, the full source code), or try building > XFree86 3.3.2 from source. In each case, I've gotten parse errors in > places with OK syntax. > > Fix > > Tried: rm -rf /usr/include /usr/src/*. Then installed full sources > and bin distribution, but the errors persisted. Seems like a bug in > the includes somewhere or in gcc 2.7.2.1 or maybe a config problem. > Maybe a bug in 2.2.6-RELEASE. > > Audit-Trail > > From: "Daniel O'Callaghan" <danny@panda.hilink.com.au> > To: dmm125@bellatlantic.net > Cc: freebsd-gnats-submit@FreeBSD.ORG > Subject: Re: gnu/6244: Lots of parse errors with gcc in 2.2.6-RELEASE > Date: Wed, 8 Apr 1998 09:25:45 +1000 (EST) > > You wouldn't be overclocking your CPU, by any chance? > Failing make world with parse errors is a sure indication of CPU > overheating, or faulty RAM. > > I have an Asus SP97-V motherboard with the SiS 5598 onboard vga which is using shared RAM (I have it configured for 4096K shared RAM). Maybe the shared ram is the culprit. I'm not overclocking the CPU. I think the shared RAM could be causing read errors on some occasions. > Danny > > /* Daniel O'Callaghan */ > /* HiLink Internet <http://www.hilink.com.au/>; danny@hilink.com.au */ > /* FreeBSD - works hard, plays hard... danny@freebsd.org */ > > > From: "Jordan K. Hubbard" <jkh@time.cdrom.com> > To: dmm125@bellatlantic.net > Cc: freebsd-gnats-submit@FreeBSD.ORG > Subject: Re: gnu/6244: Lots of parse errors with gcc in 2.2.6-RELEASE > Date: Tue, 07 Apr 1998 17:20:23 -0700 > > I can't reproduce this one at all - all my 2.2.6 builds work great. > Are you sure you're not doing something out of the ordinary here > somewhere? > It could be a configuration error. Since I ftp'd the distributions to my DOS partition, it's possible that there was a error somewhere when extracting it. I'll have to try a video card instead of the shared RAM and/or disabling the CPU cache as a check. It's a motherboard with shared RAM for the onboard video. > Jordan > > Submit Followup > ------------------------------------------------------------------------ > www@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199804080730.AAA07767>