public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kevin Shanahan <kmshanah@disenchant.net>
To: gcc-help@gcc.gnu.org
Subject: gcc 4.1 -O1 problem
Date: Thu, 16 Mar 2006 04:49:00 -0000	[thread overview]
Message-ID: <20060316044903.GE9176@cubit> (raw)

Hi,

I've come across a problem with my program when compiling with gcc-4.1
as opposed to gcc-4.0. With 4.1, the sound output comes out as
corrupted. I've narrowed it down to a single source file, and the fact
that it works with -O0 but not -O1.

However, I've tried to find the specific optimisation flag that is
causing the issue and I've come up against the situation below:

If I compile with -O0 and each of the flags below, the sound output is
working again. If I compile with -O1 and each of the options below
changed to -fno-... then the sound corruption is back:

          -fdefer-pop 
          -fdelayed-branch 
          -fguess-branch-probability 
          -fcprop-registers 
          -floop-optimize 
          -fif-conversion 
          -fif-conversion2 
          -ftree-ccp 
          -ftree-dce 
          -ftree-dominator-opts 
          -ftree-dse 
          -ftree-ter 
          -ftree-lrs 
          -ftree-sra 
          -ftree-copyrename 
          -ftree-fre 
          -ftree-ch 
          -fmerge-constants

Are there any other options besides these which -O1 affects?
Any other ideas as to how I can narrow down the cause?

Thanks,
Kevin.

             reply	other threads:[~2006-03-16  4:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-16  4:49 Kevin Shanahan [this message]
2006-03-16  5:57 ` Ian Lance Taylor
2006-03-16  6:11   ` Kevin Shanahan
2006-03-16 12:50     ` John Love-Jensen
2006-03-16 18:38       ` Kevin Shanahan

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=20060316044903.GE9176@cubit \
    --to=kmshanah@disenchant.net \
    --cc=gcc-help@gcc.gnu.org \
    /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).