From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: G++ 4.3.4 (with Cygwin 1.7) vs.G++ 4.5.2 (with MinGW) ???
Date: Tue, 14 Jun 2011 01:05:00 -0000 [thread overview]
Message-ID: <4DF6B3D4.9050406@cygwin.com> (raw)
In-Reply-To: <BANLkTimb2p-n7gDbu1Ru_PPhBdBPgc96yg@mail.gmail.com>
On 6/13/2011 2:46 AM, Jan Chludzinski wrote:
> Just finished compiling some numerical code (developed using the
> Borland C++ compiler) using G++ 4.3.4 (that came with Cygwin 1.7).
> The answers are different from what I get using the Borland compiler
> (circa 2002). I have known correct answers from some NASA code and
> compare against those.
>
> I've transitioned of late to Code::Blocks using the latest MinGW.
> MinGW comes with G++ 4.5.2. I compiled using this compiler and it
> once again it works (I get the same answers as the NASA code).
>
> Are there known problems with G++ 4.3.4?
>
> BTW, the original code was infinite looping until I replaced the old style:
>
> for (i=0; i<WHATEVER; i++) ..
>
> with i declared within the routine (i.e., function) with:
>
> for (int i=0; i<WHATEVER; i++) ...
Try turning off optimizations or at least drop back to -O3.
--
Larry
_____________________________________________________________________
A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2011-06-14 1:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 6:46 Jan Chludzinski
2011-06-14 1:05 ` Larry Hall (Cygwin) [this message]
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=4DF6B3D4.9050406@cygwin.com \
--to=reply-to-list-only-lh@cygwin.com \
--cc=cygwin@cygwin.com \
/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).