linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Dibyendu Majumdar <mobile@majumdar.org.uk>
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
	Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: sparse-llvm array size computation issue
Date: Wed, 29 Mar 2017 09:41:06 -0700	[thread overview]
Message-ID: <CA+55aFyD9NJBHONUqw2RAu0YLZ-ZeLj71gq7WYdkFRjFkvhA7w@mail.gmail.com> (raw)
In-Reply-To: <CACXZuxeRuqdinWsLXuxwwZgsMs0vHhphDk3rsC3qzww2d6SXEg@mail.gmail.com>

On Wed, Mar 29, 2017 at 9:21 AM, Dibyendu Majumdar
<mobile@majumdar.org.uk> wrote:
>
> I am trying out an approach. If a SYM_NODE has a base type of SYM_NODE
> then which of the nodes should be used as the source for information
> you mention?

Does that actually happen? It shouldn't. A symbol node contains the C
name of the symbol, but you should never have a SYM_NODE that points
to another SYM_NODE, it always points to some actual type (ie ptr,
whatever).

So the rule should be that the node can have specific information
about that particular named symbol (so: name, array size, modifiers,
address space, initializer etc), and then the node->ctype.base_type
should point to a non-NODE symbol describing the base type.

But maybe I forget some special case. Things like 'typeof() can be
complicated, but we should be peeling things off so that we only ever
have one level of SYM_NODE.

                Linus

  reply	other threads:[~2017-03-29 16:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-28 20:25 sparse-llvm array size computation issue Dibyendu Majumdar
2017-03-28 20:41 ` Dibyendu Majumdar
2017-03-28 20:49   ` Luc Van Oostenryck
2017-03-28 21:06     ` Dibyendu Majumdar
2017-03-28 21:14       ` Dibyendu Majumdar
2017-03-28 21:33         ` Luc Van Oostenryck
2017-03-28 21:43           ` Dibyendu Majumdar
2017-03-28 22:21             ` Luc Van Oostenryck
2017-03-29 11:32               ` Dibyendu Majumdar
2017-03-29 14:41                 ` Dibyendu Majumdar
2017-03-29 15:10                   ` Luc Van Oostenryck
2017-03-29 16:21                     ` Dibyendu Majumdar
2017-03-29 16:41                       ` Linus Torvalds [this message]
2017-03-29 18:12                         ` Dibyendu Majumdar
2017-03-29 20:24                           ` Dibyendu Majumdar
2017-12-28 21:30         ` Luc Van Oostenryck

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=CA+55aFyD9NJBHONUqw2RAu0YLZ-ZeLj71gq7WYdkFRjFkvhA7w@mail.gmail.com \
    --to=torvalds@linux-foundation.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=luc.vanoostenryck@gmail.com \
    --cc=mobile@majumdar.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).