public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <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: Tue, 08 Feb 2011 20:14:00 -0000	[thread overview]
Message-ID: <bug-47650-4-hNaooh4ctP@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 #4 from Andrew Pinski <pinskia at gcc dot gnu.org> 2011-02-08 20:10:43 UTC ---
(In reply to comment #3)
> I am reporting the bug that print_generic_decl() is behaving incorrectly for
> some kinds of declarations. This should either be fixed or a comment be placed
> in the source code that warns about the usage of this function (and ideally
> propose a better one).

Well I think you need to debug it to see why it is printing out static, it
might because a bit on tree has not been set yet.


  parent reply	other threads:[~2011-02-08 20:11 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 middle-end/47650] " pinskia at gcc dot gnu.org
2011-02-08 19:13 ` [Bug c/47650] " joe at mcknight dot de
2011-02-08 20:11 ` [Bug middle-end/47650] " joe at mcknight dot de
2011-02-08 20:14 ` pinskia at gcc dot gnu.org [this message]
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
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-hNaooh4ctP@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).