delorie.com/archives/browse.cgi | search |
X-Authentication-Warning: | delorie.com: mail set sender to djgpp-bounces using -f |
From: | Claude Freeman <sdoom4 AT gmail DOT com> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: CC1.EXE/GCC.EXE crashes with SIGILL, hard. |
Date: | Tue, 13 Mar 2012 21:31:56 -0700 (PDT) |
Organization: | http://groups.google.com |
Lines: | 20 |
Message-ID: | <28317907.8789.1331699516910.JavaMail.geo-discussion-forums@vbbed8> |
References: | <16777375 DOT 1302 DOT 1331688966231 DOT JavaMail DOT geo-discussion-forums AT vbat19> |
<83k42nx24b DOT fsf AT gnu DOT org> <1905590 DOT 781 DOT 1331699335277 DOT JavaMail DOT geo-discussion-forums AT vbyj18> | |
NNTP-Posting-Host: | 24.181.125.157 |
Mime-Version: | 1.0 |
X-Trace: | posting.google.com 1331699521 29241 127.0.0.1 (14 Mar 2012 04:32:01 GMT) |
X-Complaints-To: | groups-abuse AT google DOT com |
NNTP-Posting-Date: | Wed, 14 Mar 2012 04:32:01 +0000 (UTC) |
Cc: | djgpp AT delorie DOT com |
In-Reply-To: | <1905590.781.1331699335277.JavaMail.geo-discussion-forums@vbyj18> |
Complaints-To: | groups-abuse AT google DOT com |
Injection-Info: | glegroupsg2000goo.googlegroups.com; posting-host=24.181.125.157; |
posting-account=7o7X4woAAABllKcaak5lVpiMF9zViaoz | |
User-Agent: | G2/1.0 |
Bytes: | 2072 |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | djgpp AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
On Tuesday, March 13, 2012 11:28:55 PM UTC-5, Claude Freeman wrote: > On Tuesday, March 13, 2012 11:01:08 PM UTC-5, Eli Zaretskii wrote: > > > From: Claude Freeman > > > Date: Tue, 13 Mar 2012 18:36:06 -0700 (PDT) > > > > > > DPMI memory available: 25832 Kb > > > DPMI swap space available: 6232 Kb > > > > This seems to be very little memory. How about using the advice in > > the FAQ to increase the memory available to DJGPP programs? GCC is a > > memory hog, so it's possible it crashes when it hits out of memory > > conditions (a bug, but one people would rarely see on a > > well-configured system). > > I did what the FAQ said, now for the results: > > DPMI memory available: 22380 Kb > DPMI swap space available: 42452 Kb Ok, rebooted and still getting a SIGILL, even though I increased the memory.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |