From: Linus Torvalds <torvalds@linux-foundation.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Christoph Lameter <cl@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
akpm@linux-foundation.org, andi@firstfloor.org,
ak@linux.intel.com, rth@twiddle.net, sfr@canb.auug.org.au,
travis@sgi.com, linux-kernel@vger.kernel.org
Subject: Re: [patch 2/8] compiler-gcc.h: add more comments to RELOC_HIDE
Date: Wed, 14 Jan 2009 19:33:32 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.0901141932290.6528@localhost.localdomain> (raw)
In-Reply-To: <200901151227.27935.rusty@rustcorp.com.au>
On Thu, 15 Jan 2009, Rusty Russell wrote:
> On Tuesday 13 January 2009 04:03:49 Christoph Lameter wrote:
> > But that is not what is occurring. We do not do &var + LARGE_OFFSET.
> > Instead one does
> >
> > ((void *)&var) + LARGE_OFFSET
> >
> > or
> > ((unsigned long)&var) + LARGE_OFFSET
> >
> > The cast should cause the C compiler to drop all assumptions about size.
>
> No, and that's the point. Sorry, at this point you need to talk to a gcc expert. As I have said, I did and I believe what he told me.
Yeah, I personally believe in the "should cause the C compiler" part, but
gcc doesn't work that way. It will remember where the value came from,
even when the pointer has been cast to something else.
Linus
next prev parent reply other threads:[~2009-01-15 3:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200901100040.n0A0eruc013680@imap1.linux-foundation.org>
[not found] ` <200901102211.45603.rusty@rustcorp.com.au>
2009-01-10 12:29 ` Ingo Molnar
2009-01-12 17:33 ` Christoph Lameter
[not found] ` <200901151227.27935.rusty@rustcorp.com.au>
2009-01-15 3:33 ` Linus Torvalds [this message]
2009-01-15 19:19 ` Christoph Lameter
2009-01-15 22:44 ` Andi Kleen
2009-01-15 20:29 ` Christoph Lameter
2009-01-15 23:15 ` Richard Henderson
2009-01-16 20:37 ` Christoph Lameter
2009-01-19 16:30 ` Richard Henderson
2009-01-21 13:50 ` Christoph Lameter
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=alpine.LFD.2.00.0901141932290.6528@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rth@twiddle.net \
--cc=rusty@rustcorp.com.au \
--cc=sfr@canb.auug.org.au \
--cc=travis@sgi.com \
/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®