From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Dibyendu Majumdar <mobile@majumdar.org.uk>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: sparse-llvm array size computation issue
Date: Thu, 28 Dec 2017 22:30:15 +0100 [thread overview]
Message-ID: <20171228213014.few7ixr2gaksrt3f@ltop.local> (raw)
In-Reply-To: <CACXZuxcozbUcY9Bot65eSXjSxCDTzVbGSqTqJwgRCit24zisWA@mail.gmail.com>
On Tue, Mar 28, 2017 at 10:14:43PM +0100, Dibyendu Majumdar wrote:
> Hi Luc,
>
> I think that there is a bug in examine_node_type() in symbol.c - it
> should set the base_type's bit_size perhaps? See the line marked as
> FIX below,
>
> /* Unsized array? The size might come from the initializer.. */
> if (bit_size < 0 && base_type->type == SYM_ARRAY) {
> struct expression *initializer = get_symbol_initializer(sym);
> if (initializer) {
> struct symbol *node_type = base_type->ctype.base_type;
> int count = count_array_initializer(S, node_type, initializer);
>
> if (node_type && node_type->bit_size >= 0)
> bit_size = array_element_offset(S->C->target, node_type->bit_size, count);
> base_type->bit_size = bit_size; /*** FIX set base_type->bit_size ***/
> }
> }
Yes, it's correct and will fix most aspects of the issue but it's
only part of the fix:
- array_size need also to be updated
- the SYM_ARRAY can't be directly updated because it can be
shared between several nodes, so it need to be duplicated
before being updated.
-- Luc
prev parent reply other threads:[~2017-12-28 21:30 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
2017-03-29 18:12 ` Dibyendu Majumdar
2017-03-29 20:24 ` Dibyendu Majumdar
2017-12-28 21:30 ` Luc Van Oostenryck [this message]
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=20171228213014.few7ixr2gaksrt3f@ltop.local \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--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).