public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/64935] [5 Regression] compare debug failure during building of Linux kernel Date: Thu, 05 Feb 2015 11:52:00 -0000 [thread overview] Message-ID: <bug-64935-4-mg90TaYwSb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64935-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64935 --- Comment #9 from Markus Trippelsdorf <trippels at gcc dot gnu.org> --- Your patch bootstraps / tests fine on ppc64. GCC_COMPARE_DEBUG=1 kernel build also succeeds. Thanks. (If you want access to ppc machines get a compile farm account: https://gcc.gnu.org/wiki/CompileFarm There are several POWER boxes available.)
next prev parent reply other threads:[~2015-02-05 11:52 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-64935-4@http.gcc.gnu.org/bugzilla/> 2015-02-04 16:41 ` [Bug target/64935] " burnus at gcc dot gnu.org 2015-02-04 16:42 ` burnus at gcc dot gnu.org 2015-02-04 17:16 ` [Bug debug/64935] " burnus at gcc dot gnu.org 2015-02-04 17:47 ` mkuvyrkov at gcc dot gnu.org 2015-02-04 19:32 ` trippels at gcc dot gnu.org 2015-02-05 9:05 ` mkuvyrkov at gcc dot gnu.org 2015-02-05 9:06 ` mkuvyrkov at gcc dot gnu.org 2015-02-05 11:52 ` trippels at gcc dot gnu.org [this message] 2015-02-07 10:54 ` trippels at gcc dot gnu.org 2015-02-09 14:28 ` rguenth at gcc dot gnu.org 2015-02-10 13:24 ` mkuvyrkov at gcc dot gnu.org 2015-02-12 20:51 ` law at redhat dot com 2015-02-12 20:53 ` law at redhat dot com 2015-02-17 9:20 ` jakub at gcc dot gnu.org 2015-02-17 9:22 ` mkuvyrkov at gcc dot gnu.org 2015-02-18 10:22 ` mkuvyrkov at gcc dot gnu.org 2015-02-18 14:35 ` trippels at gcc dot gnu.org 2015-02-19 14:37 ` jakub 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-64935-4-mg90TaYwSb@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).