public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "diego at biurrun dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/15386] New: WMA decoder miscompiled with -O4 -mcpu=k6 - one pop, no sound
Date: Wed, 12 May 2004 18:11:00 -0000	[thread overview]
Message-ID: <20040511205714.15386.diego@biurrun.de> (raw)

MPlayer triggers another compiler bug...

The WMA (Windows Media audio codec) decoder of FFmpeg/libavcodec
(http://ffmpeg.org) wmadec.c gets miscompiled by gcc versions >=3.1 when
compiled with -mcpu=k6 and/or -O1 or above.  When playing a WMA sample with
MPlayer all you get is pop at the beginning and then no sound.  The problem
disappears with either -mcpu=pentium-mmx or -O0 (changing one parameter is
enough to make the problem go away, either one works).

Here is the complete command line and output when compiling the file:

/var/tmp/gcc-3.5-20040502/bin/gcc -I../libvo/ -I../../libvo -I/usr/X11R6/include
-g -O4 -march=k6 -mcpu=k6 -pipe -ffast-math -fomit-frame-pointer -D_REENTRANT
-I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include
-DHAVE_AV_CONFIG_H -I.. -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_GNU_SOURCE
-Wall -save-temps -c -o wmadec.o wmadec.c && make && cd .. && make
gcc: warning: -pipe ignored because -save-temps specified
`-mcpu=' is deprecated. Use `-mtune=' or '-march=' instead.

I have tried several gcc versions, 2.95.3 and 3.0.4 are OK, 3.1, 3.1.1, 3.2.3,
3.3.2, 3.4.0 and 3.5.0-20040502 all display the problem.

gcc -v output:
Configured with: ../gcc-3.1/configure --prefix=/var/tmp/gcc-3.1/
Thread model: single
gcc version 3.1

I put the file together with all the headers necessary to compile it, the .o and
.i files and a sample to test the broken sound with MPlayer on my homepage:

http://www.mplayerhq.hu/~diego/gcc/

If you require further info or testing I will be more than happy to provide it.

-- 
           Summary: WMA decoder miscompiled with -O4 -mcpu=k6 - one pop, no
                    sound
           Product: gcc
           Version: 3.5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: diego at biurrun dot de
                CC: gcc-bugs at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15386


             reply	other threads:[~2004-05-11 20:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-12 18:11 diego at biurrun dot de [this message]
2004-05-12 19:07 ` [Bug c/15386] " diego at biurrun dot de
2004-05-12 19:18 ` pinskia at gcc dot gnu dot org
2004-05-12 19:19 ` diego at biurrun dot de
2004-05-12 19:33 ` [Bug optimization/15386] " ebotcazou at gcc dot gnu dot org
2004-05-12 21:37 ` diego at biurrun dot de
2004-05-13  0:53 ` pinskia at gcc dot gnu dot org
2004-05-13  0:56 ` diego at biurrun dot de
2004-05-13  1:32 ` bangerth at dealii dot org
2004-05-15 21:18 ` [Bug rtl-optimization/15386] " ebotcazou at gcc dot gnu dot org
2004-07-18 11:07 ` diego at biurrun dot de
2004-07-18 12:08 ` diego at biurrun dot de
2004-07-18 14:25 ` pinskia at gcc dot gnu dot org
2004-07-19  0:49 ` diego at biurrun dot de
2004-07-19  1:19 ` pinskia at gcc dot gnu dot org
2004-07-19 11:50 ` diego at biurrun dot de

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=20040511205714.15386.diego@biurrun.de \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).