public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Srini Eravelli <eravelli@qualcomm.com>
To: gcc@gcc.gnu.org
Subject: Internal compiler error with ppc860 based compiler
Date: Wed, 20 Sep 2000 11:35:00 -0000	[thread overview]
Message-ID: <4.3.1.2.20000920112718.00b5aee0@jittlov.qualcomm.com> (raw)

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

             reply	other threads:[~2000-09-20 11:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-20 11:35 Srini Eravelli [this message]
2000-09-20 12:01 ` Jan Dvorak
2000-09-20 14:02 Mike Stump

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4.3.1.2.20000920112718.00b5aee0@jittlov.qualcomm.com \
    --to=eravelli@qualcomm.com \
    --cc=gcc@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).