Linux SPARSE checker discussions
 help / color / mirror / Atom feed
From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>,
	Christopher Li <sparse@chrisli.org>
Subject: Re: [PATCH] sparse: option to print compound global data symbol info
Date: Sun, 21 Jan 2018 05:27:03 +0100	[thread overview]
Message-ID: <20180121042702.sinboahtsdngkojv@ltop.local> (raw)
In-Reply-To: <80f9f805-fb35-65d6-4a86-ebe0b740fe58@infradead.org>

On Sat, Jan 20, 2018 at 07:36:24PM -0800, Randy Dunlap wrote:
> From: Randy Dunlap <rdunlap@infradead.org>
> with help from Linus. (many moons ago)
> 
> sparse addition to print all compound/composite global data symbols
> with their sizes and alignment.
> 
> usage: -list-symbols
> Example: (in kernel tree)
>   make C=2 CF="-list-symbols" arch/x86_64/kernel/smpboot.o
>   arch/x86/kernel/smpboot.c:99:1: struct cpuinfo_x86 [addressable] [noderef] [toplevel] <asn:3>cpu_info: compound size 240, alignment 8

If this only lists compound symbols, it seems a bit strange to me
to use '-list-symbols' as the option name. Maybe you could go one
step further an have '-list-symbols=compound' and if needed it can
be extended to '-list-symbols=all'.

> --- orig/sparse.c
> +++ next/sparse.c
> @@ -36,6 +36,7 @@
>  #include "allocate.h"
>  #include "token.h"
>  #include "parse.h"
> +#include "ptrlist.h"

Not really needed as it's already included indirectly but it
won't hurt, of course.

> +extern int list_symbols;

Not needed since already declared in lib.h.

> +static void list_all_symbols(struct symbol_list *list)
> +{
> +	struct symbol *sym;
> +
> +	FOR_EACH_PTR(list, sym) {
> +		/* Only show arrays, structures, unions, enums, & typedefs */
> +		if (!(sym->namespace & (NS_STRUCT | NS_TYPEDEF | NS_SYMBOL)))
> +			continue;
> +		/* Only show types we actually examined (ie used) */
> +		if (!sym->bit_size)
> +			continue;

Even after being examined, 'bit_size' can stay zero if there is
some errors. You can directly use 'if (!sym->examined)' if you
want but I think it's better to adjust the comment.

> +		if (sym->type == SYM_FN || sym->type == SYM_ENUM)
> +			continue;
> +		if (!sym->ctype.base_type)
> +			continue;
> +		if (sym->ctype.base_type->type == SYM_FN)
> +			continue;
> +		if (sym->ctype.base_type->type == SYM_ENUM)
> +			continue;
> +		if (sym->ctype.base_type->type == SYM_BASETYPE)
> +			continue;

It's a bit dangereous here. You should check for SYM_NODE.
I also think it would be better and simpler to use the helpers
is_func_type(), is_int_type(), ... or add is_compound_type().

> +		/* Don't show unnamed types */
> +		if (!sym->ident)
> +			continue;
> +		info(sym->pos, "%s: compound size %u, alignment %lu",
> +			show_typename(sym),
> +			sym->bit_size >> 3,

bits_to_bytes() should be used here.


Regards,
Luc Van Oostenryck

  reply	other threads:[~2018-01-21  4:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-21  3:36 [PATCH] sparse: option to print compound global data symbol info Randy Dunlap
2018-01-21  4:27 ` Luc Van Oostenryck [this message]
2018-01-23 10:46   ` Christopher Li
2018-01-25  6:15     ` Randy Dunlap

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=20180121042702.sinboahtsdngkojv@ltop.local \
    --to=luc.vanoostenryck@gmail.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sparse@chrisli.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