public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/39213] [4.4/4.5/4.6 regression] Preprocessor ICE with -m64 and --traditional-cpp Date: Thu, 24 Jun 2010 11:52:00 -0000 [thread overview] Message-ID: <20100624115130.31909.qmail@sourceware.org> (raw) In-Reply-To: <bug-39213-13830@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from jakub at gcc dot gnu dot org 2010-06-24 11:51 ------- note->type == 10 is: *d = '\n'; /* A sentinel note that should never be processed. */ add_line_note (buffer, d + 1, '\n'); buffer->next_line = s + 1; created. But, as this PR lacks a testcase (well, the testcase depends on a proprietary header file not included here), it is hard to guess what's going on. Can you see if doing just cp /usr/include/stdlib.h /tmp/stdlib.h gcc -E -traditional-cpp /tmp/stdlib.h If yes, can you distill a smaller testcase from it (ideally at most a few lines)? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39213
next prev parent reply other threads:[~2010-06-24 11:52 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-02-17 4:28 [Bug preprocessor/39213] New: [4.4 Regression] " rob1weld at aol dot com 2009-02-17 21:51 ` [Bug preprocessor/39213] " pinskia at gcc dot gnu dot org 2010-03-19 20:33 ` ro at gcc dot gnu dot org 2010-06-20 2:11 ` [Bug preprocessor/39213] Regression [3.4.3] " rob1weld at aol dot com 2010-06-21 12:36 ` [Bug preprocessor/39213] [4.4/4.5/4.6 regression] " ro at gcc dot gnu dot org 2010-06-24 11:52 ` jakub at gcc dot gnu dot org [this message] 2010-06-24 12:20 ` ro at CeBiTec dot Uni-Bielefeld dot DE 2010-06-24 12:56 ` jakub at gcc dot gnu dot org 2010-06-24 13:50 ` ro at CeBiTec dot Uni-Bielefeld dot DE 2010-06-25 16:48 ` ro at CeBiTec dot Uni-Bielefeld dot DE 2010-07-14 17:27 ` rob1weld at aol dot com [not found] <bug-39213-4@http.gcc.gnu.org/bugzilla/> 2010-09-30 11:58 ` rguenth at gcc dot gnu.org 2010-11-22 23:17 ` ebotcazou at gcc dot gnu.org 2010-11-24 12:04 ` ebotcazou at gcc dot gnu.org 2010-11-24 12:46 ` ebotcazou at gcc dot gnu.org 2010-11-29 9:06 ` ebotcazou at gcc dot gnu.org 2010-12-17 10:46 ` jakub at gcc dot gnu.org 2010-12-18 17:35 ` ebotcazou at gcc dot gnu.org 2010-12-18 17:37 ` ebotcazou at gcc dot gnu.org 2011-01-04 23:18 ` ebotcazou at gcc dot gnu.org 2011-01-04 23:19 ` ebotcazou at gcc dot gnu.org 2011-01-04 23:19 ` ebotcazou at gcc dot gnu.org 2011-01-04 23:20 ` ebotcazou at gcc dot gnu.org 2011-01-05 16:45 ` rob1weld at aol dot com
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=20100624115130.31909.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).