public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kcc at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/59402] [4.9 Regression] bootstrap failure on x32 Date: Fri, 06 Dec 2013 11:30:00 -0000 [thread overview] Message-ID: <bug-59402-4-gIbgZ0lEYE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59402-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59402 --- Comment #3 from Kostya Serebryany <kcc at gcc dot gnu.org> --- (In reply to H.J. Lu from comment #2) > (In reply to Kostya Serebryany from comment #1) > > Thanks for the report, H.J. I'll try to respond properly on Monday (-ish). > > Can I check my patches into trunk to unblock x32 build and revert them > after we find a better fix? You may, assuming other targets will not break. But I will not be able to do another merge until the two versions (upstream and GCC) are equivalent again. So, please don't close this bug until it's done. > > > Long term, everyone would benefit if you could setup a public build bot > > upstream. > > Can you find a machine with Ubuntu 13.04 or newer? No, sorry.
next prev parent reply other threads:[~2013-12-06 11:30 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-12-05 21:29 [Bug sanitizer/59402] New: " hjl.tools at gmail dot com 2013-12-05 21:29 ` [Bug sanitizer/59402] " hjl.tools at gmail dot com 2013-12-06 3:53 ` kcc at gcc dot gnu.org 2013-12-06 11:30 ` kcc at gcc dot gnu.org [this message] 2013-12-06 11:39 ` hjl.tools at gmail dot com 2014-01-09 21:01 ` jakub at gcc dot gnu.org 2014-01-09 21:35 ` hjl.tools at gmail dot com 2014-01-09 21:43 ` [Bug sanitizer/59402] " jakub at gcc dot gnu.org 2014-01-13 11:28 ` kcc at gcc dot gnu.org 2014-01-13 17:32 ` hjl.tools at gmail dot com 2014-04-22 11:37 ` jakub at gcc dot gnu.org 2014-07-16 13:31 ` jakub at gcc dot gnu.org 2014-10-30 10:41 ` jakub at gcc dot gnu.org 2015-02-07 14:10 ` hjl.tools at gmail 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=bug-59402-4-gIbgZ0lEYE@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).