From: Christopher Li <sparse@chrisli.org>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-sparse@vger.kernel.org
Subject: Re: fun with declarations and definitions
Date: Mon, 2 Feb 2009 19:07:24 -0800 [thread overview]
Message-ID: <70318cbf0902021907w634ffc6dm693022b23a0eabfc@mail.gmail.com> (raw)
In-Reply-To: <20090202073018.GB28946@ZenIV.linux.org.uk>
On Sun, Feb 1, 2009 at 11:30 PM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> Anyway, proposed patch for (1) follows:
I read the patch, seems reasonable. It is only solve the inline case though.
The more generic problem still exist, symbol look up between partial
prototype declare and the real declare will get symbol with partial
information.
It would be great if we can apply the definition to the first symbol. But
I can haven't find a clean way to do it yet.
Most likely I will apply your patch until we find a better way to do it.
> @@ -2282,6 +2295,7 @@ struct token *external_declaration(struct token *token, struct symbol_list **lis
> }
> }
> } else if (base_type && base_type->type == SYM_FN) {
> + if (decl->next_id && decl->next_id->scope == decl->scope)
Not sure what this is trying to do. Shouldn't the next line to be indented
if I read it correctly?
Chris
next prev parent reply other threads:[~2009-02-03 3:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-02 7:30 fun with declarations and definitions Al Viro
2009-02-02 20:17 ` Christopher Li
2009-02-02 20:58 ` Al Viro
2009-02-02 22:25 ` Christopher Li
2009-02-03 3:07 ` Christopher Li [this message]
2009-02-03 4:13 ` Al Viro
2009-02-05 18:40 ` Christopher Li
2009-02-05 18:47 ` Derek M Jones
2009-02-05 20:28 ` Al Viro
2009-02-05 21:19 ` Al Viro
2009-02-06 5:36 ` Al Viro
2009-02-09 7:52 ` Christopher Li
2009-02-09 8:54 ` Al Viro
2009-02-05 22:41 ` Christopher Li
2009-02-05 23:22 ` Al Viro
2009-02-03 4:41 ` Al Viro
2009-02-03 6:28 ` Ralf Wildenhues
2009-02-05 18:52 ` Christopher Li
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=70318cbf0902021907w634ffc6dm693022b23a0eabfc@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=linux-sparse@vger.kernel.org \
--cc=viro@zeniv.linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.