From: Al Viro <viro@ftp.linux.org.uk>
To: Josh Triplett <josht@linux.vnet.ibm.com>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [RFC] show_type() format problems
Date: Thu, 12 Jul 2007 19:25:08 +0100 [thread overview]
Message-ID: <20070712182508.GZ21668@ftp.linux.org.uk> (raw)
In-Reply-To: <1184257330.3000.7.camel@josh-work.beaverton.ibm.com>
On Thu, Jul 12, 2007 at 09:22:10AM -0700, Josh Triplett wrote:
> Please do go ahead and change the output. I'd love for show_type to
> output something as close to a parsable C type as possible.
How does below sound? At least it makes output unambiguous and much
closer to normal C syntax. We could do better (e.g. lift the things
like "extern", etc. in front of everything else), but that's a separate
problem...
diff --git a/show-parse.c b/show-parse.c
index aae8b74..9a1f796 100644
--- a/show-parse.c
+++ b/show-parse.c
@@ -226,11 +226,28 @@ const char *builtin_ctypename(struct ctype *ctype)
return NULL;
}
-static void do_show_type(struct symbol *sym, struct type_name *name)
+static void do_show_type(struct symbol *sym, struct type_name *name,
+ unsigned long mod, int as, int was_ptr)
{
- int modlen;
- const char *mod;
const char *typename;
+ int is_ptr = was_ptr;
+
+ if (!sym || (sym->type != SYM_NODE && sym->type != SYM_ARRAY &&
+ sym->type != SYM_BITFIELD)) {
+ const char *s;
+ size_t len;
+
+ if (as)
+ prepend(name, "<asn:%d>", as);
+
+ s = modifier_string(mod);
+ len = strlen(s);
+ name->start -= len;
+ memcpy(name->start, s, len);
+ mod = 0;
+ as = 0;
+ }
+
if (!sym)
return;
@@ -246,9 +263,14 @@ static void do_show_type(struct symbol *sym, struct type_name *name)
switch (sym->type) {
case SYM_PTR:
prepend(name, "*");
+ mod = sym->ctype.modifiers;
+ as = sym->ctype.as;
+ is_ptr = 1;
break;
case SYM_FN:
- prepend(name, "( ");
+ if (was_ptr)
+ prepend(name, "( ");
+ is_ptr = 0;
break;
case SYM_STRUCT:
prepend(name, "struct %s ", show_ident(sym->ident));
@@ -264,9 +286,13 @@ static void do_show_type(struct symbol *sym, struct type_name *name)
case SYM_NODE:
append(name, "%s", show_ident(sym->ident));
+ mod |= sym->ctype.modifiers;
+ as |= sym->ctype.as;
break;
case SYM_BITFIELD:
+ mod |= sym->ctype.modifiers;
+ as |= sym->ctype.as;
append(name, ":%d", sym->bit_size);
break;
@@ -275,6 +301,11 @@ static void do_show_type(struct symbol *sym, struct type_name *name)
break;
case SYM_ARRAY:
+ mod |= sym->ctype.modifiers;
+ as |= sym->ctype.as;
+ if (was_ptr)
+ prepend(name, "( ");
+ is_ptr = 0;
break;
case SYM_RESTRICT:
@@ -288,26 +319,21 @@ static void do_show_type(struct symbol *sym, struct type_name *name)
return;
}
- mod = modifier_string(sym->ctype.modifiers);
- modlen = strlen(mod);
- name->start -= modlen;
- memcpy(name->start, mod, modlen);
-
- do_show_type(sym->ctype.base_type, name);
-
- /* Postpend */
- if (sym->ctype.as)
- append(name, "<asn:%d>", sym->ctype.as);
+ do_show_type(sym->ctype.base_type, name, mod, as, is_ptr);
switch (sym->type) {
case SYM_PTR:
- return;
+ return;
case SYM_FN:
- append(name, " )( ... )");
+ if (was_ptr)
+ append(name, " )");
+ append(name, "( ... )");
return;
case SYM_ARRAY:
+ if (was_ptr)
+ append(name, " )");
append(name, "[%lld]", get_expression_value(sym->array_size));
return;
@@ -330,7 +356,7 @@ void show_type(struct symbol *sym)
struct type_name name;
name.start = name.end = array+100;
- do_show_type(sym, &name);
+ do_show_type(sym, &name, 0, 0, 0);
*name.end = 0;
printf("%s", name.start);
}
@@ -341,7 +367,7 @@ const char *show_typename(struct symbol *sym)
struct type_name name;
name.start = name.end = array+100;
- do_show_type(sym, &name);
+ do_show_type(sym, &name, 0, 0, 0);
*name.end = 0;
return name.start;
}
prev parent reply other threads:[~2007-07-12 18:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 9:14 [RFC] show_type() format problems Al Viro
2007-07-12 16:22 ` Josh Triplett
2007-07-12 18:25 ` Al Viro [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=20070712182508.GZ21668@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=josht@linux.vnet.ibm.com \
--cc=linux-sparse@vger.kernel.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 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.