public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/47650] wrong output of print_generic_decl() called from a plugin
Date: Wed, 16 Mar 2011 09:40:00 -0000 [thread overview]
Message-ID: <bug-47650-4-9wugHgHVVl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47650-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47650
--- Comment #24 from rguenther at suse dot de <rguenther at suse dot de> 2011-03-16 09:38:37 UTC ---
On Tue, 15 Mar 2011, joe at mcknight dot de wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47650
>
> --- Comment #23 from joe at mcknight dot de 2011-03-15 17:05:24 UTC ---
> (In reply to comment #22)
> > > Compare it to:
> > >
> > > typedef int mytype;
> > > int myfunc2(mytype var) {
> > > return 1;
> > > };
> > >
> > > which outputs
> > >
> > > static int myfunc2 (mytype);
> > >
> > > i.e. returns the newly created type as well.
> >
> > That's by design.
>
> Then what is the design rule behind it, for me it looks inconsistent to once
> inline the original type and another time use the newly created type.
>
>
> > > It outputs "static void (*Handler) (int, void *) GetFunctionPointer (void);"
> >
> > It's not designed to do that. The functions are for debugging and
> > diagnostic output only, they are not supposed to generate valid C.
>
> I know, but instead of creating a new language, wouldn't it be good to just
> stick to the C grammar to describe what is being seen?
>
>
>
> Was the debug output helpful with respect to the wrong variadic output?
Well, it confirmed that void_list_node is not used, but I can't
reproduce this fact.
next prev parent reply other threads:[~2011-03-16 9:38 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 19:09 [Bug c/47650] New: " joe at mcknight dot de
2011-02-08 19:13 ` [Bug c/47650] " joe at mcknight dot de
2011-02-08 19:13 ` [Bug middle-end/47650] " pinskia at gcc dot gnu.org
2011-02-08 20:11 ` joe at mcknight dot de
2011-02-08 20:14 ` pinskia at gcc dot gnu.org
2011-02-08 20:22 ` joe at mcknight dot de
2011-02-09 10:56 ` rguenth at gcc dot gnu.org
2011-02-09 14:26 ` joe at mcknight dot de
2011-02-09 16:27 ` joe at mcknight dot de
2011-02-09 16:45 ` rguenther at suse dot de
2011-02-09 18:09 ` joe at mcknight dot de
2011-02-09 18:14 ` joe at mcknight dot de
2011-02-09 18:31 ` joe at mcknight dot de
2011-02-10 22:51 ` joe at mcknight dot de
2011-03-15 13:41 ` rguenth at gcc dot gnu.org
2011-03-15 13:42 ` rguenth at gcc dot gnu.org
2011-03-15 15:53 ` joe at mcknight dot de
2011-03-15 15:56 ` joe at mcknight dot de
2011-03-15 16:00 ` rguenth at gcc dot gnu.org
2011-03-15 16:03 ` rguenth at gcc dot gnu.org
2011-03-15 16:15 ` joe at mcknight dot de
2011-03-15 16:22 ` joe at mcknight dot de
2011-03-15 16:36 ` rguenther at suse dot de
2011-03-15 17:06 ` joe at mcknight dot de
2011-03-16 9:40 ` rguenther at suse dot de [this message]
2011-03-16 13:07 ` joe at mcknight dot de
2011-03-16 13:32 ` rguenther at suse dot de
2011-03-16 14:41 ` joe at mcknight dot de
2011-03-17 20:08 ` joe at mcknight dot de
2011-04-06 17:55 ` joe at mcknight dot de
2011-04-28 16:08 ` rguenth at gcc dot gnu.org
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=bug-47650-4-9wugHgHVVl@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).