public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "uros at kss-loka dot si" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/16111] generates invalid SSE movdqa instruction (instead of movaps)
Date: Tue, 21 Dec 2004 06:42:00 -0000 [thread overview]
Message-ID: <20041221064242.4209.qmail@sourceware.org> (raw)
In-Reply-To: <20040621114206.16111.djp@volny.cz>
------- Additional Comments From uros at kss-loka dot si 2004-12-21 06:42 -------
Mainline does not generate movdqa insn anymore. However:
g++ -O1 -msse -mfpmath=sse -fomit-frame-pointer -finline-limit=2000 pr16111.cpp
./a.out
extents (-27.500000 -27.500000 -0.000000 -0.000000)
g++ -O2 -msse -mfpmath=sse -fomit-frame-pointer -finline-limit=2000 pr16111.cpp
./a.out
extents (0.000000 0.000000 2.018096 2.018096)
g++ -O3 -msse -mfpmath=sse -fomit-frame-pointer -finline-limit=2000 pr16111.cpp
./a.out
extents (0.000000 0.000000 36.658997 36.658997)
Result is different, it depends on optimization level.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16111
next prev parent reply other threads:[~2004-12-21 6:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-21 11:42 [Bug translation/16111] New: " djp at volny dot cz
2004-06-21 15:09 ` [Bug target/16111] " bangerth at dealii dot org
2004-06-21 16:34 ` pinskia at gcc dot gnu dot org
2004-06-21 17:18 ` djp at volny dot cz
2004-06-21 17:40 ` pinskia at gcc dot gnu dot org
2004-07-25 17:35 ` drober32 at fau dot edu
2004-09-21 12:53 ` coyote at coyotegulch dot com
2004-12-21 3:41 ` pinskia at gcc dot gnu dot org
2004-12-21 6:42 ` uros at kss-loka dot si [this message]
2004-12-21 15:25 ` uros at kss-loka dot si
2004-12-28 6:33 ` uros at kss-loka dot si
2004-12-29 0:32 ` rth at gcc dot gnu dot org
2004-12-29 0:35 ` pinskia at gcc dot gnu dot org
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=20041221064242.4209.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).