From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13702 invoked by alias); 25 Jun 2013 22:23:30 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 13670 invoked by uid 48); 25 Jun 2013 22:23:25 -0000 From: "manu at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/57714] Newline rendered incorrectly in output Date: Tue, 25 Jun 2013 22:23:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: preprocessor X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: manu at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2013-06/txt/msg01520.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D57714 Manuel L=C3=B3pez-Ib=C3=A1=C3=B1ez changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |manu at gcc dot gnu.org --- Comment #4 from Manuel L=C3=B3pez-Ib=C3=A1=C3=B1ez --- (In reply to David Krauss from comment #0) > main(){\ > return 0; > } >=20 > preprocesses to >=20 > main(){return > 0; > } Actually, according to: http://gcc.gnu.org/wiki/FAQ#cpp_continuation_discar= ded I am surprised the backslash is not simply discarded. It is discarded if you add a space before the "return". It is a bug that it is NOT discarded, >>From gcc-bugs-return-425142-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jun 25 22:26:16 2013 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 14963 invoked by alias); 25 Jun 2013 22:26:16 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 14928 invoked by uid 48); 25 Jun 2013 22:26:10 -0000 From: "duncan_roe at acslink dot net.au" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/57707] gcc misinterprets hex escapes in constant strings Date: Tue, 25 Jun 2013 22:26:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 4.7.1 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: duncan_roe at acslink dot net.au X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2013-06/txt/msg01521.txt.bz2 Content-length: 678 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57707 duncan_roe at acslink dot net.au changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|INVALID |--- --- Comment #5 from duncan_roe at acslink dot net.au --- There's no need for that. C is defined in Kernighan & Ritchie's "The C Programming Language". They mandate \xhh as a character escape. No mention of "except when the next character happens to be a hex digit".