public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/44578] GCC generates MMX instructions but fails to generate "emms" Date: Fri, 18 Jun 2010 10:46:00 -0000 [thread overview] Message-ID: <20100618104613.1639.qmail@sourceware.org> (raw) In-Reply-To: <bug-44578-19343@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from rguenth at gcc dot gnu dot org 2010-06-18 10:46 ------- As -mfpmath=sse isn't supposed to change the ABI we should never emit MMX instructions automagically. -- rguenth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Keywords| |wrong-code Last reconfirmed|0000-00-00 00:00:00 |2010-06-18 10:46:13 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44578
next prev parent reply other threads:[~2010-06-18 10:46 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-06-18 10:27 [Bug target/44578] New: " stephen dot dolan at havok dot com 2010-06-18 10:46 ` rguenth at gcc dot gnu dot org [this message] 2010-06-19 17:23 ` [Bug target/44578] " ubizjak at gmail dot com [not found] <bug-44578-4@http.gcc.gnu.org/bugzilla/> 2012-11-15 6:36 ` kl4yfd at gmail dot com 2012-11-15 6:39 ` kl4yfd at gmail dot com 2012-11-15 12:06 ` jakub at gcc dot gnu.org 2012-11-15 17:05 ` kl4yfd at gmail dot com 2013-04-29 16:44 ` tejohnson at google dot com 2013-04-29 17:13 ` ubizjak at gmail dot com 2013-04-29 17:24 ` tejohnson at google dot com 2013-04-29 17:37 ` ubizjak at gmail dot com 2013-04-30 5:38 ` ubizjak at gmail dot com 2013-04-30 5:43 ` tejohnson at google dot com 2013-04-30 5:53 ` ubizjak at gmail dot com 2013-04-30 6:07 ` ubizjak at gmail dot com
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=20100618104613.1639.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: linkBe 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).