Linux SPARSE checker discussions
 help / color / mirror / Atom feed
From: Al Viro <viro@ftp.linux.org.uk>
To: linux-sparse@vger.kernel.org
Subject: Re: pointer arithmetics and casts
Date: Fri, 25 May 2007 23:00:51 +0100	[thread overview]
Message-ID: <20070525220051.GO4095@ftp.linux.org.uk> (raw)
In-Reply-To: <20070525212300.GL4095@ftp.linux.org.uk>

On Fri, May 25, 2007 at 10:23:00PM +0100, Al Viro wrote:
> 	BINOP[+]
> 		<tree for p>
> 		BINOP[*]
> 			IMPLICIEDT_CAST[ptrdiff_t]
> 				<tree for i>
> 			VAL[sizeof(*p)]
> 
> But that means a fsckload of extra nodes allocated on pretty much any
> program - use of arrays is not rare and indices tend to be int, so we
> hit an extra allocated node on each such place.

Argh...  Question: how much do we care if we see BINOP[+] with 64bit
type as result and 32bit type in one of the arguments?  That's what
we get when we have
	char *p;
	int i;

	p + i

with -m64.  IOW, how much does it violate the assumptions outside of
frontend?  We do not allocate any new nodes if sizeof(*p) is 1...

  reply	other threads:[~2007-05-25 22:00 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 [this message]
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
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=20070525220051.GO4095@ftp.linux.org.uk \
    --to=viro@ftp.linux.org.uk \
    --cc=linux-sparse@vger.kernel.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