From: Richard Henderson <rth@redhat.com>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: Ingo Molnar <mingo@elte.hu>, Andrew Morton <akpm@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>, Andi Kleen <ak@suse.de>
Subject: Re: [patch] i386: make bitops safe
Date: Tue, 28 Feb 2006 13:25:38 -0800 [thread overview]
Message-ID: <20060228212538.GA28302@redhat.com> (raw)
In-Reply-To: <200602280106_MC3-1-B974-9231@compuserve.com>
On Tue, Feb 28, 2006 at 01:04:01AM -0500, Chuck Ebbert wrote:
> > One could reasonably argue that if you used a structure with a
> > flexible array member, that GCC could not look through that. But
> > again I'm not 100% positive this is handled properly.
>
> This seems to work but causes more problems than it solves:
>
> #define vaddr ((volatile long *) addr)
This isn't a structure witha flexible array member.
r~
next prev parent reply other threads:[~2006-02-28 21:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-28 6:04 [patch] i386: make bitops safe Chuck Ebbert
2006-02-28 21:25 ` Richard Henderson [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-27 21:57 Chuck Ebbert
2006-02-27 23:06 ` Linus Torvalds
2006-02-27 23:47 ` Andi Kleen
2006-02-28 0:54 ` Richard Henderson
2006-02-28 1:24 ` Andi Kleen
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=20060228212538.GA28302@redhat.com \
--to=rth@redhat.com \
--cc=76306.1226@compuserve.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@osdl.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