From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: linux-kernel@alex.org.uk
Cc: engler@csl.Stanford.EDU (Dawson Engler),
alan@lxorguk.ukuu.org.uk (Alan Cox),
nave@stanford.edu (Evan Parker),
linux-kernel@vger.kernel.org, mc@CS.Stanford.EDU
Subject: Re: [CHECKER] repetitive/contradictory comparison bugs for 2.4.7
Date: Thu, 26 Jul 2001 23:06:02 +0100 (BST) [thread overview]
Message-ID: <E15PtGc-0004ad-00@the-village.bc.nu> (raw)
In-Reply-To: <602725597.996180886@[169.254.62.211]> from "Alex Bligh - linux-kernel" at Jul 26, 2001 08:54:48 PM
> How will this be guaranteed to help handle a race, when gcc is
> likely either to have tmp_buf in a register (not declared
> volatile), or perhaps even optimize out the second reference.
The function call is a synchronization point, and the function it calls
might change the value. I put the barriers into my tree to make this clear
although I cant see some future super gcc globally optimising that one
anyway
Alan
next prev parent reply other threads:[~2001-07-26 22:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-25 0:08 Evan Parker
2001-07-25 0:51 ` Neil Brown
2001-07-25 8:27 ` Russell King
2001-07-25 13:34 ` Alan Cox
2001-07-26 1:13 ` Dawson Engler
2001-07-26 19:54 ` Alex Bligh - linux-kernel
2001-07-26 20:15 ` Russell King
2001-07-26 22:07 ` Alan Cox
2001-07-26 22:06 ` Alan Cox [this message]
2001-07-26 22:24 ` Alex Bligh - linux-kernel
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=E15PtGc-0004ad-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=engler@csl.Stanford.EDU \
--cc=linux-kernel@alex.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mc@CS.Stanford.EDU \
--cc=nave@stanford.edu \
/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
all inboxes | Powered by JetHome®