public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl dot tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/39533] -MM may list a header file twice
Date: Mon, 30 Mar 2009 21:27:00 -0000 [thread overview]
Message-ID: <20090330212646.27410.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39533-682@http.gcc.gnu.org/bugzilla/>
------- Comment #10 from hjl dot tools at gmail dot com 2009-03-30 21:26 -------
(In reply to comment #9)
> It is not really a bug, but it is ugly.
>
Is there anything wrong with my patch?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39533
next prev parent reply other threads:[~2009-03-30 21:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 21:37 [Bug preprocessor/39533] New: " hjl dot tools at gmail dot com
2009-03-23 21:40 ` [Bug preprocessor/39533] " pinskia at gcc dot gnu dot org
2009-03-23 21:44 ` hjl dot tools at gmail dot com
2009-03-24 1:48 ` pinskia at gcc dot gnu dot org
2009-03-24 1:50 ` pinskia at gcc dot gnu dot org
2009-03-24 17:26 ` hjl dot tools at gmail dot com
2009-03-24 17:26 ` hjl dot tools at gmail dot com
2009-03-24 17:44 ` hjl dot tools at gmail dot com
2009-03-24 17:49 ` rwild at gcc dot gnu dot org
2009-03-30 21:23 ` tromey at gcc dot gnu dot org
2009-03-30 21:27 ` hjl dot tools at gmail dot com [this message]
2009-03-30 21:50 ` tromey at gcc dot gnu dot org
2009-07-15 7:30 ` [Bug preprocessor/39533] [4.4/4.5 Regression] " steven at gcc dot gnu dot org
2009-07-15 7:31 ` steven at gcc dot gnu dot org
2009-07-29 22:31 ` jsm28 at gcc dot gnu dot org
2009-10-15 12:55 ` jakub at gcc dot gnu dot org
2010-01-21 13:18 ` jakub at gcc dot gnu dot org
2010-04-30 9:00 ` [Bug preprocessor/39533] [4.4/4.5/4.6 " jakub at gcc dot gnu dot 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=20090330212646.27410.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).