delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2015/10/24/14:46:36

X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:content-type;
bh=HdcN9ZgUtTORjeaY7ZMjtGN420r6a342LNVEnm/srz8=;
b=EXR0ZkBFGwbSbtcvW0Umd9X8qegUEAsajV7ua7vQG2UgU+Zf8nKRNMyHVXSLH6QEm5
Q1kh0wpsBHabzNgMzogSIo2onc2uLrAG++g6EooaKqDt7hxei8x7ZOJW1RSupL3MDELu
OfmcAkX0sLu9hpce7U/nwMBEdJq7kh73ybEyWSTG9INHrDAGxxPSUbKDjmNZq0LiMeHe
3Etbq6lQMB/MhlCmQg74+fG92ALPqXNH7Ab2M/ov0ywxJSAKeOOiC2OypYVNGjSj86PD
tvbCIlVCuogKK/zOBASHGbSSCHTqzQ96rzu117sO3i0+X7yv5i3Jbh6QXtXeK9wm2iXn
Q3yw==
MIME-Version: 1.0
X-Received: by 10.50.50.232 with SMTP id f8mr10965307igo.66.1445712384587;
Sat, 24 Oct 2015 11:46:24 -0700 (PDT)
In-Reply-To: <562BCDB5.8000402@iki.fi>
References: <562BCDB5 DOT 8000402 AT iki DOT fi>
Date: Sat, 24 Oct 2015 11:46:24 -0700
Message-ID: <CAB9Rao_2QazAWzGWU5nxVHzCQvXi7n4Ni2A008VGvHq9UuKXVg@mail.gmail.com>
Subject: Re: DJGPP v2.05 and Windows 10
From: "Louis Santillan (lpsantil AT gmail DOT com) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
To: "djgpp AT delorie DOT com" <djgpp AT delorie DOT com>
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

Andris, is it possible that you have a bad memory chip?  Maybe
something in 4.x, 5.x, 6.x gcc grows the memory image into the bad
pages while 3.x does not and/or does utilize (read/write) those bad
pages.

On Sat, Oct 24, 2015 at 11:28 AM, Andris Pavenis
(andris DOT pavenis AT iki DOT fi) [via djgpp AT delorie DOT com] <djgpp AT delorie DOT com>
wrote:
> Did some additional tests on WIndows 10.
>
> I'm getting random compile failures with gcc-4.9.3, gcc4.5.2 and gcc 6.0.0
> 20151018 experimental (last development version I built for DJGPP).
> Running
>
> echo '#include <iostream>" | gcc -E -dD -x c++ -
>
> in loop and comparing outputs is sufficient for detecting random corruption.
> I have not succeeded to find why it happens and how to workaround that.
> Additionally I'm also getting random failures when trying to repeatedly
> compile same preprocessed C++ file.
>
> The situation is however not completely hopeless:
> Installed gcc-3.4.6 and bootstrapped the same gcc version (3.4.6) without
> problems under Windows 10. No random gcc failures observed.
>
> So some difference (or differences) between gcc-3.4.6 and recent version
> cause problems.
> Some suspects:
> - change to C++ as implementation language
> - noticeable increase of size of executables and resources required by them
>
> Andris
>
>
>
>
>

- Raw text -


  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019