public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mmitchel at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/8270] [3.4/4.0/4.1/4.2 Regression] back-slash white space newline with comments, no warning Date: Sat, 11 Mar 2006 03:20:00 -0000 [thread overview] Message-ID: <20060311031832.22043.qmail@sourceware.org> (raw) In-Reply-To: <bug-8270-4718@http.gcc.gnu.org/bugzilla/> -- mmitchel at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|4.0.3 |4.0.4 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=8270
next prev parent reply other threads:[~2006-03-11 3:20 UTC|newest] Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-8270-4718@http.gcc.gnu.org/bugzilla/> 2005-10-25 23:45 ` [Bug preprocessor/8270] back-slash newline extension can't be removed pinskia at gcc dot gnu dot org 2005-10-25 23:45 ` pinskia at gcc dot gnu dot org 2005-10-25 23:46 ` pinskia at gcc dot gnu dot org 2005-10-26 0:24 ` echristo at apple dot com 2005-10-26 0:25 ` echristo at apple dot com 2005-10-26 0:26 ` echristo at apple dot com 2005-10-26 0:43 ` pinskia at gcc dot gnu dot org 2005-10-26 0:45 ` pinskia at gcc dot gnu dot org 2005-10-26 0:46 ` [Bug preprocessor/8270] [3.4/4.0/4.1 Regression] " pinskia at gcc dot gnu dot org 2005-10-26 0:46 ` pinskia at gcc dot gnu dot org 2005-10-26 0:58 ` pinskia at gcc dot gnu dot org 2005-10-26 1:02 ` pinskia at gcc dot gnu dot org 2005-10-26 1:05 ` pinskia at gcc dot gnu dot org 2005-10-26 1:10 ` pinskia at gcc dot gnu dot org 2005-10-26 1:17 ` pinskia at gcc dot gnu dot org 2005-10-26 1:31 ` pinskia at gcc dot gnu dot org 2005-10-26 1:33 ` pinskia at gcc dot gnu dot org 2005-10-26 1:37 ` pinskia at gcc dot gnu dot org 2005-10-26 1:39 ` pinskia at gcc dot gnu dot org 2005-10-26 1:42 ` pinskia at gcc dot gnu dot org 2005-10-26 1:59 ` pinskia at gcc dot gnu dot org 2005-10-26 2:00 ` pinskia at gcc dot gnu dot org 2005-10-26 2:12 ` pinskia at gcc dot gnu dot org 2005-10-26 6:29 ` pinskia at gcc dot gnu dot org 2005-10-26 21:42 ` pinskia at gcc dot gnu dot org 2005-10-26 21:46 ` echristo at apple dot com 2005-10-26 21:49 ` pinskia at gcc dot gnu dot org 2005-10-26 23:07 ` Neil Booth 2005-10-26 23:07 ` neil at daikokuya dot co dot uk 2005-10-26 23:13 ` dj at redhat dot com 2005-10-30 21:43 ` [Bug preprocessor/8270] [3.4/4.0/4.1 Regression] back-slash white space newline with comments, no warning mmitchel at gcc dot gnu dot org 2006-03-11 3:20 ` mmitchel at gcc dot gnu dot org [this message] 2006-06-08 21:12 ` [Bug preprocessor/8270] [4.0/4.1/4.2 " echristo at apple dot com 2007-01-18 2:37 ` [Bug preprocessor/8270] [4.0/4.1/4.2/4.3 " gdr at gcc dot gnu dot org 2007-01-21 21:17 ` pinskia at gcc dot gnu dot org 2007-02-14 9:29 ` mmitchel at gcc dot gnu dot org 2008-07-04 16:29 ` [Bug preprocessor/8270] [4.2/4.3/4.4 " jsm28 at gcc dot gnu dot org 2008-12-07 1:02 ` pinskia at gcc dot gnu dot org 2008-12-07 1:03 ` pinskia at gcc dot gnu dot org 2009-03-31 16:12 ` [Bug preprocessor/8270] [4.3/4.4/4.5 " jsm28 at gcc dot gnu dot org 2009-08-04 12:27 ` rguenth at gcc dot gnu dot org 2009-08-17 17:42 ` jessiecute13 at aol dot com 2010-05-22 18:11 ` [Bug preprocessor/8270] [4.3/4.4/4.5/4.6 " rguenth at gcc dot gnu dot org 2010-06-01 18:25 ` pinskia 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=20060311031832.22043.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).