public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "falk at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/22076] Strange code for MMX register moves
Date: Wed, 15 Jun 2005 12:57:00 -0000	[thread overview]
Message-ID: <20050615125655.32217.qmail@sourceware.org> (raw)
In-Reply-To: <20050615123954.22076.uros@kss-loka.si>


------- Additional Comments From falk at debian dot org  2005-06-15 12:56 -------
(In reply to comment #0)
> This testcase:
> #include <mmintrin.h>
> 
> __m64 test() {
>    __m64 a;
> 
>    return a;
> }

Well, this is invalid code, so it's not really important what the code
looks like. If it also occurs in valid code, it might be related to PR 7061.


-- 


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


  reply	other threads:[~2005-06-15 12:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-15 12:40 [Bug target/22076] New: " uros at kss-loka dot si
2005-06-15 12:57 ` falk at debian dot org [this message]
2005-06-15 17:35 ` [Bug target/22076] " pinskia at gcc dot gnu dot org
2005-06-21 12:04 ` uros at kss-loka dot si
2005-06-21 13:06 ` pinskia at gcc dot gnu dot org
2005-06-22 20:27 ` pinskia at gcc dot gnu dot org
2005-06-22 20:29 ` pinskia at gcc dot gnu dot org
2005-08-31 19:18 ` pinskia at gcc dot gnu dot org
2005-08-31 20:42 ` bangerth at dealii dot org
     [not found] <bug-22076-1649@http.gcc.gnu.org/bugzilla/>
2007-12-10  8:40 ` ubizjak at gmail dot com
2008-02-23 15:25 ` uros at gcc dot gnu dot org
2008-02-23 15:34 ` ubizjak at gmail dot com
2008-03-08  7:24 ` ubizjak at gmail dot com
2008-11-16  0:14 ` howarth at nitro dot med dot uc dot edu
2008-11-16  0:15 ` howarth at nitro dot med dot uc dot edu

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=20050615125655.32217.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).