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: compiler does not issue emmx
Date: Tue, 15 Jan 2002 04:26:00 -0000	[thread overview]
Message-ID: <20020115122624.15852.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 <David.Kastrup@t-online.de>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: target/5381: compiler does not issue emmx
Date: Tue, 15 Jan 2002 04:16:03 -0800

 On Tue, Jan 15, 2002 at 09:07:37AM +0100, David Kastrup wrote:
 > If the user put emmx instructions in at a place where the compiler
 > decided to leave a variable in an MMX register for optimization purposes...
 
 Nope.  The __builtin_emmx function clobbers all of the mmx registers,
 so the compiler knows that any spillage must happen before that.
 
 
 r~


             reply	other threads:[~2002-01-15 12:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-15  4:26 Richard Henderson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-15  0:16 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=20020115122624.15852.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).