public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gdr at cs dot tamu dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/33255] A warning for "unused" typedefs?
Date: Fri, 31 Aug 2007 00:06:00 -0000 [thread overview]
Message-ID: <20070831000555.2815.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33255-133@http.gcc.gnu.org/bugzilla/>
------- Comment #7 from gdr at cs dot tamu dot edu 2007-08-31 00:05 -------
Subject: Re: A warning for "unused" typedefs?
On Thu, 30 Aug 2007, pcarlini at suse dot de wrote:
| Well, assuming there are no "no-go" theorems about that problem ;) I would be
| certainly interested in studying the problem in better detail...
I did not mean to imply that the problem is unsolvable or NP-complete
or something like that. I just pointed out that usually we rely on
(1) data flow insfrastructure,
(2) uniqueness of entities refered to by variable and functions
to warn about unused declarations.
Typedefs on the other hand can be "folded" in very early on. So, one
needs to track that folding...
-- Gaby
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33255
next prev parent reply other threads:[~2007-08-31 0:06 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 23:21 [Bug c++/33255] New: " pcarlini at suse dot de
2007-08-30 23:30 ` [Bug c++/33255] " pinskia at gcc dot gnu dot org
2007-08-30 23:33 ` pcarlini at suse dot de
2007-08-30 23:43 ` gdr at cs dot tamu dot edu
2007-08-30 23:46 ` pcarlini at suse dot de
2007-08-30 23:51 ` gdr at cs dot tamu dot edu
2007-08-30 23:59 ` pcarlini at suse dot de
2007-08-31 0:06 ` gdr at cs dot tamu dot edu [this message]
2007-08-31 0:34 ` fang at csl dot cornell dot edu
2007-08-31 1:04 ` gdr at cs dot tamu dot edu
2007-08-31 8:41 ` pcarlini at suse dot de
2007-08-31 8:44 ` pcarlini at suse dot de
[not found] <bug-33255-16141@http.gcc.gnu.org/bugzilla/>
2008-06-09 13:37 ` paolo dot carlini at oracle dot com
2008-06-09 14:07 ` gdr at cs dot tamu dot edu
[not found] <bug-33255-4@http.gcc.gnu.org/bugzilla/>
2011-07-22 16:50 ` dodji at gcc dot gnu.org
2011-07-22 17:01 ` paolo.carlini at oracle dot com
2011-07-24 21:59 ` dodji at gcc dot gnu.org
2011-07-24 22:10 ` dodji at gcc dot gnu.org
2011-07-24 22:34 ` paolo.carlini at oracle dot com
2011-07-24 22:38 ` paolo.carlini at oracle dot com
2011-07-24 22:50 ` paolo.carlini at oracle dot com
2011-07-24 22:54 ` paolo.carlini at oracle dot com
2011-07-25 11:18 ` dodji at seketeli dot org
2011-07-25 11:44 ` paolo.carlini at oracle dot com
2011-07-25 14:29 ` dodji at seketeli dot org
2011-07-25 17:32 ` dodji at gcc dot gnu.org
2011-07-27 18:10 ` dodji at gcc dot gnu.org
2011-09-08 13:57 ` dodji at gcc dot gnu.org
2011-09-08 21:22 ` dodji at seketeli dot org
2011-11-07 17:53 ` jason at gcc dot gnu.org
2012-08-22 21:00 ` paolo.carlini at oracle dot com
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=20070831000555.2815.qmail@sourceware.org \
--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).