public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Brown <david@westcontrol.com>
Cc: Oleg Endo <oleg.endo@t-online.de>, Andrew Haley <aph@redhat.com>,
	<gcc-help@gcc.gnu.org>
Subject: Re: GCC vs MSVC compiler issues in a port
Date: Thu, 27 Dec 2012 13:10:00 -0000	[thread overview]
Message-ID: <50DC48C6.5010204@westcontrol.com> (raw)
In-Reply-To: <50D6991B.1070904@yahoo.com>

On 23/12/12 06:39, John Cotton Ericson wrote:
> On 12/22/2012 11:30 AM, Andrew Haley wrote:
>> You need to start with an unoptimized build; does it crash in the same
>> way? What about building with -Wall ?
> I have been using no optimization other than -ffast-math. Whether or not
> I used -msse and -march=native or -mi386 I get arithmetic overflows
> without -ffast-math.
> 
> I am looking at the warnings with -Wall. Nothing too interesting but
> I'll try to resolve them.
> 

There are more warning flags in gcc than just -Wall - perhaps some
others will give you new clues (though there might be a lot of "noise",
especially with old code).  Also note that many of the gcc warnings only
work well when you have optimisation enabled, as they depend on some of
the analysis passes in the optimiser.  So try at least "-O2 -Wall -Wextra".


  reply	other threads:[~2012-12-27 13:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <50D57597.7050304@yahoo.com>
2012-12-22  9:07 ` John Cotton Ericson
2012-12-22 12:11   ` Oleg Endo
2012-12-23  5:39     ` John Cotton Ericson
2012-12-27 13:10       ` David Brown [this message]
2012-12-28 23:46       ` Oleg Endo
2013-01-18 22:31         ` John Cotton Ericson
2012-12-22 16:31   ` Andrew Haley

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=50DC48C6.5010204@westcontrol.com \
    --to=david@westcontrol.com \
    --cc=aph@redhat.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=oleg.endo@t-online.de \
    /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).