public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at physics dot uc dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/11628] movd support for _mm_cvtsi32_si64 and _mm_cvtsi64_si32
Date: Tue, 22 Jul 2003 13:04:00 -0000	[thread overview]
Message-ID: <20030722130449.12222.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030722041707.11628.dean-gcc@arctic.org>

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

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


pinskia at physics dot uc dot edu changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
          Component|c                           |target
     Ever Confirmed|                            |1
           Keywords|                            |pessimizes-code
   Last reconfirmed|0000-00-00 00:00:00         |2003-07-22 13:04:49
               date|                            |


------- Additional Comments From pinskia at physics dot uc dot edu  2003-07-22 13:04 -------
Could you send you patch to gcc-patches@gcc.gnu.org after reading 
<http://gcc.gnu.org/contribute.html>.

I can confirm his way is much faster.


  reply	other threads:[~2003-07-22 13:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-22  4:17 [Bug c/11628] New: " dean-gcc at arctic dot org
2003-07-22 13:04 ` pinskia at physics dot uc dot edu [this message]
2003-07-22 16:45 ` [Bug target/11628] " dean-gcc at arctic dot org
2003-07-23 20:19 ` pinskia at physics dot uc dot edu
2003-07-23 20:34 ` otaylor at redhat dot com
2003-07-23 20:38 ` pinskia at physics dot uc dot edu
2003-07-23 21:46 ` dean-gcc at arctic dot org
2003-08-23 23:15 ` pinskia at gcc dot gnu dot org
2003-08-23 23:22 ` pinskia at gcc dot gnu dot org
2004-11-30 14:58 ` uros at kss-loka dot si
2005-01-13  9:26 ` uros at kss-loka dot si

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=20030722130449.12222.qmail@sources.redhat.com \
    --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).