public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "krejzi at email dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/65713] New: C Preprocessor generates invalid output Date: Thu, 09 Apr 2015 13:41:00 -0000 [thread overview] Message-ID: <bug-65713-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65713 Bug ID: 65713 Summary: C Preprocessor generates invalid output Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: blocker Priority: P3 Component: preprocessor Assignee: unassigned at gcc dot gnu.org Reporter: krejzi at email dot com Created attachment 35274 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35274&action=edit gcc-4.9.2 output Using GCC snapshot 5.0.0 20150405 (experimental) and trying to build libgpg-error-1.18, which generates a header file using the output from gcc -E on a header file. Output from gcc-4.9.2 and the mentioned snapshot is different, which causes libgpg-error to fail to compile. gcc-4.9.2 gives the output from first.txt mentioned snapshot gives the output from second.txt The header file used in both examples is the third attachment.
next reply other threads:[~2015-04-09 13:41 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-09 13:41 krejzi at email dot com [this message] 2015-04-09 13:42 ` [Bug preprocessor/65713] " krejzi at email dot com 2015-04-09 13:43 ` krejzi at email dot com 2015-04-09 13:46 ` mpolacek at gcc dot gnu.org 2015-04-09 13:55 ` krejzi at email dot com 2015-04-09 13:57 ` mpolacek at gcc dot gnu.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-65713-4@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).