From: Oleg Nesterov <oleg@redhat.com>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: Alexey Gladkov <gladkov.alexey@gmail.com>, linux-sparse@vger.kernel.org
Subject: Re: [PATCH] dissect: add support for _Generic
Date: Thu, 30 Jul 2020 17:08:37 +0200 [thread overview]
Message-ID: <20200730150837.GA6956@redhat.com> (raw)
In-Reply-To: <20200729145025.g26jqfpqcnhd5wed@ltop.local>
On 07/29, Luc Van Oostenryck wrote:
>
> > + break; case EXPR_GENERIC: {
> > + struct type_expression *map;
> > +
> > + do_expression(U_VOID, expr->control);
> > +
> > + for (map = expr->map; map; map = map->next)
> > + ret = do_expression(mode, map->expr);
> > + if (expr->def)
> > + ret = do_expression(mode, expr->def);
> > + }
> > +
> > break; case EXPR_SYMBOL:
> > ret = report_symbol(mode, expr);
> > }
>
> Yes, that should do the 'walking'.
OK, I am sending this stupid patch. Better than nothing.
> The returned type will just be
> quite arbitrary, but I don't know how much it matters.
Of course. And this is not good. For example:
void func(void)
{
struct B *b; struct C *c; struct D *d;
_Generic(a,
int: b,
void*: c,
default: d
) ->mem++;
}
output:
1:6 def f func void ( ... )
3:18 func def . v b struct B *
3:31 func def . v c struct C *
3:44 func def . v d struct D *
4:18 func --- v a bad type
5:33 func --m . v b struct B *
6:33 func --m . v c struct C *
7:33 func --m . v d struct D *
8:11 func -m- m D.mem bad type
But I do not know how to improve it without serious complications, and
(so far) I think it doesn't worth the effort.
Oleg.
next prev parent reply other threads:[~2020-07-30 15:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 18:35 [PATCH] dissect: add support for _Generic Alexey Gladkov
2020-07-28 19:49 ` Oleg Nesterov
2020-07-28 23:10 ` Luc Van Oostenryck
2020-07-29 11:28 ` Oleg Nesterov
2020-07-29 14:50 ` Luc Van Oostenryck
2020-07-30 15:08 ` Oleg Nesterov [this message]
2020-07-30 20:00 ` Luc Van Oostenryck
2020-07-31 14:43 ` Oleg Nesterov
2020-07-31 16:13 ` Luc Van Oostenryck
2020-07-30 15:09 ` [PATCH] dissect: support _Generic() a bit more Oleg Nesterov
2020-07-30 20:05 ` 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=20200730150837.GA6956@redhat.com \
--to=oleg@redhat.com \
--cc=gladkov.alexey@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
/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).