From: Mike Stump <mrs@windriver.com>
To: eravelli@qualcomm.com, gcc@gcc.gnu.org
Subject: Re: Internal compiler error with ppc860 based compiler
Date: Wed, 20 Sep 2000 14:02:00 -0000 [thread overview]
Message-ID: <200009202101.OAA26438@kankakee.wrs.com> (raw)
> 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.
next reply other threads:[~2000-09-20 14:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-20 14:02 Mike Stump [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-09-20 11:35 Srini Eravelli
2000-09-20 12:01 ` Jan Dvorak
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=200009202101.OAA26438@kankakee.wrs.com \
--to=mrs@windriver.com \
--cc=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).