public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* Internal compiler error with ppc860 based compiler
@ 2000-09-20 11:35 Srini Eravelli
  2000-09-20 12:01 ` Jan Dvorak
  0 siblings, 1 reply; 3+ messages in thread
From: Srini Eravelli @ 2000-09-20 11:35 UTC (permalink / raw)
  To: gcc

We are trying to compile some C++ code for PPC860 processor. We are using 
the following version of the compiler:

Reading specs from 
C:\Apps\Tornado2\host\x86-win32\lib\gcc-lib\powerpc-wrs-vxworks\cygnus-2.7.2-960126\specs
gcc driver version cygnus-2.7.2-960126 egcs-971225 tornado 2.0 executing 
gcc version cygnus-2.7.2-960126

The compiler gave the following error message:

(C:\Apps\Tornado2\host\x86-win32\lib\gcc-lib\powerpc-wrs-vxworks\cygnus-2.7.2-960126\cc1plus.exe 
1000) Exception: STATUS
_ACCESS_VIOLATION
(C:\Apps\Tornado2\host\x86-win32\lib\gcc-lib\powerpc-wrs-vxworks\cygnus-2.7.2-960126\cc1plus.exe 
1000) Dumping stack tra
ce to cc1plus.exe.core
ccppc: Internal compiler error: program cc1plus got fatal signal 0
make[1]: *** [OBJPPC860/bscsim.o] Error 0x1
make[1]: Leaving directory `V:\warp\development\src\bts\test\framework'
make: *** [/warp/development/src/bts/test/framework/btst.PPC860.a] Error 0x2

    I can send the core file generated by the compiler if any one is 
interested in looking at it. Has anyone run into this error. If so, do you 
know of a work around or a version that has the fix.
thanks
--Srini

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Internal compiler error with ppc860 based compiler
  2000-09-20 11:35 Internal compiler error with ppc860 based compiler Srini Eravelli
@ 2000-09-20 12:01 ` Jan Dvorak
  0 siblings, 0 replies; 3+ messages in thread
From: Jan Dvorak @ 2000-09-20 12:01 UTC (permalink / raw)
  To: Srini Eravelli; +Cc: gcc

On Wed, Sep 20, 2000 at 11:34:16AM -0700, Srini Eravelli wrote:
> We are trying to compile some C++ code for PPC860 processor. We are using 
> the following version of the compiler:
> 
> Reading specs from 
> C:\Apps\Tornado2\host\x86-win32\lib\gcc-lib\powerpc-wrs-vxworks\cygnus-2.7.2-960126\specs
> gcc driver version cygnus-2.7.2-960126 egcs-971225 tornado 2.0 executing 
> gcc version cygnus-2.7.2-960126
You are using more than 4 year old compiler. Try to upgrade to gcc 2.95.2
first. 

> 
>     I can send the core file generated by the compiler if any one is 
> interested in looking at it. Has anyone run into this error. If so, do you 
> know of a work around or a version that has the fix.
> thanks
> --Srini

Core files are not much usable outside your system, rather, send
preprocessed file which this error came from. Please read
http://gcc.gnu.org/bugs.html for more details.

Jan Dvorak <johnydog@go.cz>


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Internal compiler error with ppc860 based compiler
@ 2000-09-20 14:02 Mike Stump
  0 siblings, 0 replies; 3+ messages in thread
From: Mike Stump @ 2000-09-20 14:02 UTC (permalink / raw)
  To: eravelli, gcc

> Date: Wed, 20 Sep 2000 11:34:16 -0700
> To: gcc@gcc.gnu.org
> From: Srini Eravelli <eravelli@qualcomm.com>

> We are trying to compile some C++ code for PPC860 processor. We are
> using the following version of the compiler:

> Has anyone run into this error.

Yes, I suspect so.

> If so, do you know of a work around or a version that has the fix.

Yes, I suspect so.  Any compiler that was new in the past year should
be ok.  Further, you should be able to ask WindRiver about this...  I
suspect 29226 is the problem if -fno-exceptions fixes the crash, or
29267 is your using -O/-O1/-O2, and -O0 fixes it, or 28424 just on
general principals.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2000-09-20 14:02 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-09-20 11:35 Internal compiler error with ppc860 based compiler Srini Eravelli
2000-09-20 12:01 ` Jan Dvorak
2000-09-20 14:02 Mike Stump

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).