From: "Ashutosh S. Rajekar" <asr@giaspna.vsnl.net.in>
To: help-gcc@gnu.org
Subject: Re: Compilation using -O2 Problem
Date: Sun, 31 Oct 1999 13:57:00 -0000 [thread overview]
Message-ID: <Pine.SOL.3.96.991009183159.6617A-100000@giaspna> (raw)
Message-ID: <19991031135700.K703o8ceR1HeZ221-Wa3sRnX_Jf_JSLIlqlJM_sMcXQ@z> (raw)
In-Reply-To: <7tiqq8$fnj$1@nntp.smartdna.com>
On Thu, 7 Oct 1999, Gerald E. Bennett wrote:
> I am trying to compile my code,
> it compiles fine when I don't use the -O2 option
> as as soon as I ue it I get the following errror:
>
> hashtabledata.cpp:38: Internal compiler error.
GCC uses many pointers when it is compiling your program. When it
just manages to screw up, either because of slow mem and fast CPU, or the
other way, it gets a SIG11, or SIGSEGV, a segmentation violation, or
internal compiler error. Just compile the program again, and it will work
smoothly.
> Why is this ?
> How can I get more compile info to know what's going on ?
Try the man page. Or you can get the gcc docs from any mirror site,
say www.djgpp.com, or whatever.
-------------------
Ashutosh S. Rajekar
http://i.am/asr
next prev parent reply other threads:[~1999-10-31 13:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-07 17:17 Gerald E. Bennett
1999-10-07 23:31 ` Tim Prince
1999-10-31 13:57 ` Tim Prince
1999-10-09 6:21 ` Ashutosh S. Rajekar [this message]
1999-10-31 13:57 ` Ashutosh S. Rajekar
1999-10-31 13:57 ` Gerald E. Bennett
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=Pine.SOL.3.96.991009183159.6617A-100000@giaspna \
--to=asr@giaspna.vsnl.net.in \
--cc=help-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).