public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl dot tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/36331] [4.4 Regression]: Gcc failed to bootstrap Date: Mon, 26 May 2008 06:58:00 -0000 [thread overview] Message-ID: <20080526065807.13559.qmail@sourceware.org> (raw) In-Reply-To: <bug-36331-682@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from hjl dot tools at gmail dot com 2008-05-26 06:58 ------- Revision 135882 is the cause. A simple testcase: [hjl@gnu-26 gcc]$ cat x.cc int main () { #ifndef __GNUG__ #error "This is bad." #endif return 0; } [hjl@gnu-26 gcc]$ gcc -c x.cc [hjl@gnu-26 gcc]$ ./xgcc -B./ -c x.cc x.cc:5:2: error: #error "This is bad." [hjl@gnu-26 gcc]$ -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36331
next prev parent reply other threads:[~2008-05-26 6:58 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-05-26 2:07 [Bug bootstrap/36331] New: " hjl dot tools at gmail dot com 2008-05-26 6:53 ` [Bug bootstrap/36331] " dfranke at gcc dot gnu dot org 2008-05-26 6:58 ` hjl dot tools at gmail dot com [this message] 2008-05-26 7:16 ` dfranke at gcc dot gnu dot org 2008-05-26 7:17 ` hjl dot tools at gmail dot com 2008-05-26 7:21 ` dfranke at gcc dot gnu dot org 2008-05-26 7:44 ` dfranke at gcc dot gnu dot org 2008-05-26 10:23 ` dfranke 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=20080526065807.13559.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).