All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Kip Walker <kwalker@broadcom.com>
Cc: linux-mips@linux-mips.org
Subject: Re: __volatile__ for asms in unaligned.c
Date: Fri, 21 Feb 2003 02:09:51 +0100	[thread overview]
Message-ID: <20030221020950.E6463@linux-mips.org> (raw)
In-Reply-To: <3E555A2E.5920F387@broadcom.com>; from kwalker@broadcom.com on Thu, Feb 20, 2003 at 02:43:58PM -0800

On Thu, Feb 20, 2003 at 02:43:58PM -0800, Kip Walker wrote:

> Anyway, is there a reason these aren't marked as volatile?  The gcc docs
> have the scary comment "You can prevent an `asm' instruction from being
> deleted, MOVED SIGNIFICANTLY, or combined, by writing the keyword
> `volatile' after the`asm'."

It's a valid code movement by gcc's no longer really new basic block
reordering thing.  I admit I'm pretty surprised this wasn't found before.

So I just added the volatiles.

  Ralf

      reply	other threads:[~2003-02-21  1:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-20 22:43 __volatile__ for asms in unaligned.c Kip Walker
2003-02-21  1:09 ` Ralf Baechle [this message]

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=20030221020950.E6463@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=kwalker@broadcom.com \
    --cc=linux-mips@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.