public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gcc-bug at andihellmund dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/44191] New: -E output broken for gcc-4.5.0 Date: Tue, 18 May 2010 22:34:00 -0000 [thread overview] Message-ID: <bug-44191-19059@http.gcc.gnu.org/bugzilla/> (raw) Hey, while working on a low-prio PR24024, I recognized that the -E output of gcc-4.5.0 is somehow "broken" for certain constructs, for example: ==== test.c ==== int main () { int ret, a; ret = a + \ b; } ==== END test.c ==== (gcc-4.5.0) # gcc -E test.c # 1 "test.c" # 1 "<built-in>" # 1 "<command-line>" # 1 "test.c" int main () { int ret, a; ret = a + b; } I also tested this on older versions of gcc and each of these versions (4.2.0, 4.3.0 and 4.4.3) return the expected output: # 1 "test.c" # 1 "<built-in>" # 1 "<command-line>" # 1 "test.c" int main () { int ret, a; ret = a + b; } I currently suspect that this incorrect output in gcc-4.5.0 is caused by _cpp_clean_line. For my understanding, _cpp_clean_line should detect the splice operator and merge the two lines to form a new logical line which is then output due to the -E option. -- Summary: -E output broken for gcc-4.5.0 Product: gcc Version: 4.5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: gcc-bug at andihellmund dot com GCC build triplet: x86_64-unknown-linux-gnu GCC host triplet: x86_64-unknown-linux-gnu GCC target triplet: x86_64-unknown-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44191
next reply other threads:[~2010-05-18 22:34 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-05-18 22:34 gcc-bug at andihellmund dot com [this message] 2010-05-18 22:45 ` [Bug preprocessor/44191] " 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=bug-44191-19059@http.gcc.gnu.org/bugzilla/ \ --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).