public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/19161] No emms or femms emitted between MMX and FP instructions
Date: Wed, 19 Mar 2008 10:39:00 -0000 [thread overview]
Message-ID: <20080319103828.27224.qmail@sourceware.org> (raw)
In-Reply-To: <bug-19161-119@http.gcc.gnu.org/bugzilla/>
------- Comment #23 from ubizjak at gmail dot com 2008-03-19 10:38 -------
As stated in comment #16 and #17, the LCM infrastructure doesn't support mode
switching in the way that would be usable for emms. Additionally, there are
MANY problems expected when sharing x87 and MMX registers (i.e. handling of
uninitialized x87 registers at the beginning of the function - this is the
reason we don't implement x87 register passing ABI).
Automatic MMX vectorization is not exactly a much usable feature nowadays (we
have SSE that works quite well here). Due to recent changes in MMX register
allocation area, excellent code is produced using MMX intrinsics, I'm closing
this bug as WONTFIX.
--
ubizjak at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19161
next prev parent reply other threads:[~2008-03-19 10:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-19161-119@http.gcc.gnu.org/bugzilla/>
2005-11-02 6:39 ` rth at gcc dot gnu dot org
2008-01-04 22:44 ` Richard dot Barnes at stratus dot com
2008-03-19 10:39 ` ubizjak at gmail dot com [this message]
2004-12-26 20:16 [Bug target/19161] New: " rth at gcc dot gnu dot org
2004-12-26 21:20 ` [Bug target/19161] " pinskia at gcc dot gnu dot org
2004-12-27 0:24 ` pinskia at gcc dot gnu dot org
2004-12-27 0:26 ` pinskia at gcc dot gnu dot org
2005-01-18 9:54 ` rth at gcc dot gnu dot org
2005-06-21 11:20 ` steven at gcc dot gnu dot org
2005-06-24 14:03 ` pluto at agmk dot net
2005-06-24 20:33 ` uros at kss-loka dot si
2005-06-25 6:26 ` pluto at agmk dot net
2005-06-25 7:40 ` uros at kss-loka dot si
2005-07-21 8:53 ` uros at kss-loka dot si
2005-07-22 9:42 ` uros at kss-loka dot si
2005-07-23 15:51 ` pluto at agmk dot net
2005-07-23 17:23 ` pluto at agmk dot net
2005-08-19 11:08 ` uros at kss-loka dot si
2005-08-22 20:43 ` rth at gcc dot gnu dot org
2005-08-23 20:56 ` rth at gcc dot gnu dot org
2005-08-23 21:38 ` rth at gcc dot gnu dot org
2005-08-24 14:46 ` uros at kss-loka dot si
2005-09-22 13:11 ` pluto at agmk dot net
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=20080319103828.27224.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).