public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rearnsha@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, gertom@rgai.hu,
	nobody@gcc.gnu.org
Subject: Re: target/9757: Gcc should use swp instruction in ARM targets
Date: Thu, 20 Feb 2003 12:13:00 -0000	[thread overview]
Message-ID: <20030220121324.26937.qmail@sources.redhat.com> (raw)

Synopsis: Gcc should use swp instruction in ARM targets

State-Changed-From-To: open->closed
State-Changed-By: rearnsha
State-Changed-When: Thu Feb 20 12:13:24 2003
State-Changed-Why:
    No, the SWP instruction should not be used.  For several reasons.
    
    1) It's very slow on some processors, since it forces an external bus access even if the data is already in the cache.
    2) It's behaviour is not defined if access is made to a MMU managed page that is non-cacheable/bufferable.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9757


             reply	other threads:[~2003-02-20 12:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-20 12:13 rearnsha [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-19 16:56 gertom

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=20030220121324.26937.qmail@sources.redhat.com \
    --to=rearnsha@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=gertom@rgai.hu \
    --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).