www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2015/06/20/11:45:07

X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Received: by 10.43.159.1 with SMTP id lw1mr20946406icc.9.1434814272378;
Sat, 20 Jun 2015 08:31:12 -0700 (PDT)
X-Received: by 10.140.39.165 with SMTP id v34mr361013qgv.25.1434814271246;
Sat, 20 Jun 2015 08:31:11 -0700 (PDT)
Newsgroups: comp.os.msdos.djgpp
Date: Sat, 20 Jun 2015 08:31:11 -0700 (PDT)
In-Reply-To: <CAA2C=vDpU5XoXZ=3MNiaE1zY8FEwGm_Cki4bd8mQpBFJ9DZ2Vw@mail.gmail.com>
Complaints-To: groups-abuse AT google DOT com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=78.45.215.78; posting-account=Q0wMHAoAAADjYrghh94FTf6YnbpTqZgp
NNTP-Posting-Host: 78.45.215.78
References: <201506091712 DOT t59HCPci004068 AT delorie DOT com> <557739E0 DOT 6070608 AT gmail DOT com>
<CAB9Rao93XrKFBpUDnZdjCz+rEXHGOU2RNKdou2oMLJOk802LnA AT mail DOT gmail DOT com>
<55775E64 DOT 2090901 AT gmail DOT com> <CAB9Rao-Njdr-CB=vqHnb+TVDmXu3eXqsB5CHB7V0kDwBEsM-WQ AT mail DOT gmail DOT com>
<5579ED42 DOT 6070309 AT gmail DOT com> <CAB9Rao8cvu3hLEf=KsRWn7woXka0F9Aax7uM9Jj5QqCO=1bL8w AT mail DOT gmail DOT com>
<5579FE8D DOT 3080501 AT gmail DOT com> <557B436F DOT 1050101 AT gmx DOT de> <fe60143b-fe03-451f-84d4-a7d59a67cefc AT googlegroups DOT com>
<d1f33445-bef3-42d5-a343-55fed9868908 AT googlegroups DOT com> <779efaf6-8ebf-4f2a-a526-a2773e3909b4 AT googlegroups DOT com>
<4131b54f-b34d-4a84-ada6-3443ed9efce9 AT googlegroups DOT com> <20150618-004800 DOT 313 DOT 0 AT Your-Name-Here DOT News>
<fda73a64-d86c-400d-a78d-4d11b067d138 AT googlegroups DOT com> <CAA2C=vCYCjih4r38XZ45TURJPxpKAF40kakFM8iRizDH08QbVQ AT mail DOT gmail DOT com>
<65ad24c7-0888-4526-9395-e262f348a021 AT googlegroups DOT com> <5584B697 DOT 60303 AT gmail DOT com>
<CAA2C=vDpU5XoXZ=3MNiaE1zY8FEwGm_Cki4bd8mQpBFJ9DZ2Vw AT mail DOT gmail DOT com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <df602366-69ab-4b0f-abe0-034278aa11b3@googlegroups.com>
Subject: Re: DJGGP 2.05 upgrade problems. (appologies)
From: "RayeR (glaux AT centrum DOT cz)" <djgpp AT delorie DOT com>
Injection-Date: Sat, 20 Jun 2015 15:31:11 +0000
Bytes: 2750
Lines: 10
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t5KFj1sa030149
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

> Is there a specific reason that you guys using gcc4 or gcc5?
> I am still happy with gcc-3.4.6...

I think it's good to keep compiler recent - bugfixes, optimization, features...
E.g. gcc 4.x can find some potential bugs in code and throw a warning while 3.x not for same code. In all my projects (my code, not just a ports) I use to have strictly 0 warnings so it's then more easy to detect a problem when warning rise instead of searching through hundreds of warnings that nobody reads anyway... But I'm also a bit conservative so I keep gcc 4.8.4 as main compiler. Also I found that 5.x produce bigger code.

- Raw text -


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