Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: David Daney <ddaney@avtrex.com>
To: David Daney <ddaney@avtrex.com>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>,
	Ralf Baechle <ralf@linux-mips.org>,
	Richard Sandiford <rsandifo@nildram.co.uk>,
	GCC Mailing List <gcc@gcc.gnu.org>,
	linux-mips@linux-mips.org
Subject: Re: MIPS atomic memory operations (A.K.A PR 33479).
Date: Wed, 19 Sep 2007 10:47:42 -0700	[thread overview]
Message-ID: <46F160BE.9030500@avtrex.com> (raw)
In-Reply-To: <46F15BB3.50107@avtrex.com>

David Daney wrote:
> Maciej W. Rozycki wrote:
>> On Wed, 19 Sep 2007, Ralf Baechle wrote:
>>
>>> Please make this loop closure branch a branch-likely.  This is necessary
>>> as a errata workaround for some processors.
>>
>>  Do we emulate them for MIPS I?  We do emulate "ll" and "sc" and 
>> adding "sync" is easy
> 
> Currently, I (and thus GCC 4.3) am assuming that Linux emulates 'll', 
> 'sc' and 'sync', If sync is not emulated, we would need to adjust the 
> code generation so that it is not emitted on ISAs that don't support it.
> 

I just checked myself.  'sync' is not emulated.  We will have to make a 
change so that it is not emitted on ISAs that do not support it.

David Daney

  parent reply	other threads:[~2007-09-19 17:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-19  0:12 MIPS atomic memory operations (A.K.A PR 33479) David Daney
2007-09-19  2:32 ` Daniel Jacobowitz
2007-09-19  8:45 ` Thiemo Seufer
2007-09-19 16:58 ` Ralf Baechle
2007-09-19 17:07   ` Maciej W. Rozycki
2007-09-19 17:26     ` David Daney
2007-09-19 17:46       ` Maciej W. Rozycki
2007-09-19 17:49         ` David Daney
2007-09-19 18:12           ` Thiemo Seufer
2007-09-19 18:28             ` Ralf Baechle
2007-09-19 17:47       ` David Daney [this message]
2007-09-19 18:08         ` Maciej W. Rozycki

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=46F160BE.9030500@avtrex.com \
    --to=ddaney@avtrex.com \
    --cc=gcc@gcc.gnu.org \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --cc=rsandifo@nildram.co.uk \
    /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