public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manfred99 at gmx dot ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/33638] optimization bug: wrong code with -fforce-addr
Date: Fri, 05 Oct 2007 09:36:00 -0000	[thread overview]
Message-ID: <20071005093624.14065.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33638-9562@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from manfred99 at gmx dot ch  2007-10-05 09:36 -------
Ok, I managed to produce a testcase: a wrapper around the miscompiled
function and all the missing routines. Input data is read from a binary file,
so the program has to be run on a x86 machine (littleendian).

I attach a tar file with all these things, including program output of a
good and a bad run.

good.out is an output of
# gcc -O2 -march=pentium4 -c mova2i.c
# gfortran -O2 -march=pentium4 -o main main.f \
    comunpack.f rdieee.f gbytesc.f mova2i.o
# ./main > good.out

bad.out likewise, but with "-O2 -march=pentium4 -fforce-addr" (the
additional flag only matters to comunpack.f, the other routines seem
not to be affected and can be compiled arbitrarily).

Hope this helps.


-- 


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


  parent reply	other threads:[~2007-10-05  9:36 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-03 12:44 [Bug middle-end/33638] New: " manfred99 at gmx dot ch
2007-10-03 12:46 ` [Bug middle-end/33638] " manfred99 at gmx dot ch
2007-10-03 12:47 ` manfred99 at gmx dot ch
2007-10-03 12:49 ` manfred99 at gmx dot ch
2007-10-03 15:43 ` ubizjak at gmail dot com
2007-10-03 20:11 ` manfred99 at gmx dot ch
2007-10-04  6:48 ` ubizjak at gmail dot com
2007-10-05  9:36 ` manfred99 at gmx dot ch [this message]
2007-10-05  9:39 ` manfred99 at gmx dot ch
2007-10-05 10:47 ` [Bug rtl-optimization/33638] [4.3 regression]: " ubizjak at gmail dot com
2007-10-05 11:40 ` ubizjak at gmail dot com
2007-10-05 11:50 ` zadeck at naturalbridge dot com
2007-10-05 12:36 ` rguenth at gcc dot gnu dot org
2007-10-05 13:03 ` zadeck at naturalbridge dot com
2007-10-05 17:50 ` kargl at gcc dot gnu dot org
2007-10-05 20:16 ` rguenth at gcc dot gnu dot org
2007-10-05 20:17 ` zadeck at naturalbridge dot com
2007-10-06  6:49 ` ubizjak at gmail dot com
2007-10-06 12:27 ` zadeck at naturalbridge dot com
2007-10-06 13:07 ` zadeck at naturalbridge dot com
2007-10-06 19:59 ` ubizjak at gmail dot com
2007-10-06 21:20 ` zadeck at naturalbridge dot com
2007-10-08  8:56 ` ubizjak at gmail dot com
2007-10-08 12:16 ` ubizjak at gmail dot com
2007-10-08 12:35 ` Kenneth dot Zadeck at NaturalBridge dot com
2007-10-11  5:33 ` ebotcazou at gcc dot gnu dot org
2007-10-11  5:39 ` [Bug rtl-optimization/33638] [4.3 regression] wrong code with -O2 -fforce-addr ebotcazou at gcc dot gnu dot org
2007-10-11  5:48 ` ubizjak at gmail dot com
2007-10-12 15:28 ` manfred99 at gmx dot ch

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=20071005093624.14065.qmail@sourceware.org \
    --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).