Linux SPARSE checker discussions
 help / color / mirror / Atom feed
From: Al Viro <viro@ftp.linux.org.uk>
To: Derek M Jones <derek@knosof.co.uk>
Cc: Morten Welinder <mwelinder@gmail.com>, linux-sparse@vger.kernel.org
Subject: Re: pointer arithmetics and casts
Date: Sat, 26 May 2007 05:16:28 +0100	[thread overview]
Message-ID: <20070526041628.GQ4095@ftp.linux.org.uk> (raw)
In-Reply-To: <4657AA5F.1020705@knosof.co.uk>

On Sat, May 26, 2007 at 04:32:47AM +0100, Derek M Jones wrote:
> This is an unsigned type, so the wrap around behavior is defined.
> But do you really want to map a small negative index into a large 
> positive one?
> 
> You probably have to use intptr_t and uintptr_t.
> 
> On the other hand if sizeof(size_t) == sizeof(type_of(tree for i))
> is an implicit cast needed?

It is not; however, on a lot of targets that doesn't really help since
the typical situation will have i smaller than p (any 64bit target with
32bit int).  So the problem of having to allocate a lot of extra nodes
remains...

FWIW, I don't think that asking which of the target's integer types is
suitable is really relevant; assuming that such type exists at all,
we can make it a parameter of target and be done with that (BTW, we
are not guaranteed that there is an integer type capable of holding
a pointer - see 7.18.1.4, it's an optional type).

  reply	other threads:[~2007-05-26  4:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-25 21:23 pointer arithmetics and casts Al Viro
2007-05-25 22:00 ` Al Viro
2007-05-26 15:45   ` Al Viro
2007-05-26  1:14 ` Morten Welinder
2007-05-26  3:32   ` Derek M Jones
2007-05-26  4:16     ` Al Viro [this message]
2007-05-26  3:43   ` Al Viro
2007-05-26  3:44 ` Neil Booth
2007-05-26  4:22   ` Al Viro
2007-05-26  4:37     ` Neil Booth

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=20070526041628.GQ4095@ftp.linux.org.uk \
    --to=viro@ftp.linux.org.uk \
    --cc=derek@knosof.co.uk \
    --cc=linux-sparse@vger.kernel.org \
    --cc=mwelinder@gmail.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