public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: target/5381: __builtin_ia32_pmulhuw seems unknown to compiler
Date: Mon, 14 Jan 2002 18:36:00 -0000	[thread overview]
Message-ID: <20020115023608.14001.qmail@sources.redhat.com> (raw)

The following reply was made to PR target/5381; it has been noted by GNATS.

From: Richard Henderson <rth@redhat.com>
To: David.Kastrup@t-online.de
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: target/5381: __builtin_ia32_pmulhuw seems unknown to compiler
Date: Mon, 14 Jan 2002 18:29:54 -0800

 On Mon, Jan 14, 2002 at 08:44:34PM -0000, David.Kastrup@t-online.de wrote:
 > Strangely, while using -mmmx, __builtin_ia32_pmulhuw is unknown to
 > the compiler, while, for example, __builtin_ia32_pmulhw seems known.
 
 Not a bug -- pmulhuw is an SSE instruction, not part of
 the base MMX instruction set.
 
 > Anyhow, as you can see from the generated code, the compiler fails to
 > emit an emmx instruction at the end of the routine, leading to possible
 > floating point errors after return.
 
 Again, not a bug.  The user is responsible for handling emmx.
 
 If the compiler were deciding to emit MMX code on its own, 
 then yes I would agree that it must clean up after itself.
 But this is not the case here.
 
 
 r~


             reply	other threads:[~2002-01-15  2:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-14 18:36 Richard Henderson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-14 18:43 rodrigc
2002-01-14 12:46 David.Kastrup

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=20020115023608.14001.qmail@sources.redhat.com \
    --to=rth@redhat.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).