public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "echristo at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/13726] [3.3/3.4/4.0 regression]cpp -C -dI loses comments on same line as #include directives Date: Tue, 01 Feb 2005 02:21:00 -0000 [thread overview] Message-ID: <20050201022129.31815.qmail@sourceware.org> (raw) In-Reply-To: <20040118012210.13726.neroden@gcc.gnu.org> ------- Additional Comments From echristo at redhat dot com 2005-02-01 02:21 ------- The best I can get without major surgery to cpp is this: #include "test.h" <contents of test.h> /* comment from include line */ Which is likely insufficient for any good needs. I think what we need to be able to do with cpplib is to put actions on a stack and have them popped at the end of the directive. Another option is to have _cpp_push_include (or push_file) finish out the current buffer before actually pushing out the file. I don't know how well this will work out in practice though. Thoughts? -- What |Removed |Added ---------------------------------------------------------------------------- CC| |zack at codesourcery dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13726
next prev parent reply other threads:[~2005-02-01 2:21 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-01-18 1:22 [Bug preprocessor/13726] New: [3.3/3.4/3.5 " neroden at gcc dot gnu dot org 2004-01-18 2:06 ` [Bug preprocessor/13726] " dhazeghi at yahoo dot com 2004-01-18 17:08 ` pinskia at gcc dot gnu dot org 2004-02-15 12:39 ` gdr at gcc dot gnu dot org 2004-03-01 1:45 ` mmitchel at gcc dot gnu dot org 2004-11-27 2:39 ` [Bug preprocessor/13726] [3.3/3.4/4.0 " neroden at gcc dot gnu dot org 2005-01-29 0:25 ` echristo at redhat dot com 2005-01-29 0:27 ` echristo at redhat dot com 2005-01-29 0:34 ` echristo at redhat dot com 2005-02-01 2:21 ` echristo at redhat dot com [this message] 2005-02-08 14:26 ` echristo at redhat dot com 2005-04-21 5:05 ` [Bug preprocessor/13726] [3.3/3.4/4.0/4.1 " mmitchel at gcc dot gnu dot org 2005-07-08 1:44 ` [Bug preprocessor/13726] [3.4/4.0/4.1 " mmitchel at gcc dot gnu dot org 2005-09-22 21:42 ` pinskia at gcc dot gnu dot org 2005-09-27 16:14 ` mmitchel 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=20050201022129.31815.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: linkBe 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).