public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "meissner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/59009] libsanitizer merge from upstream r191666 breaks bootstrap on powerpc64-linux Date: Tue, 12 Nov 2013 17:32:00 -0000 [thread overview] Message-ID: <bug-59009-4-LJpgqbyIW5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59009-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59009 Michael Meissner <meissner at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner at gcc dot gnu.org --- Comment #4 from Michael Meissner <meissner at gcc dot gnu.org> --- It has been a week since you broke the build for powerpc64 and other targets. Please immediately revert these patches to allow the ports to build while you work on patches that will not break on the major host/targets. Quoting from the GCC development plan. If a patch is committed which introduces a regression on any target which the Steering Committee considers to be important and if: the problem is reported to the original poster; 48 hours pass without the original poster or any other party indicating that a fix will be forthcoming in the very near future; two people with write privileges to the affected area of the compiler determine that the best course of action is to revert the patch; then they may revert the patch. (The list of important targets will be revised at the beginning of each release cycle, if necessary, and is part of the release criteria.) After the patch has been reverted, the poster may appeal the decision to the Steering Committee. Note that no distinction is made between patches which are themselves buggy and patches that expose latent bugs elsewhere in the compiler.
next prev parent reply other threads:[~2013-11-12 17:32 UTC|newest] Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-11-05 18:36 [Bug sanitizer/59009] New: " bergner at gcc dot gnu.org 2013-11-06 11:47 ` [Bug sanitizer/59009] " rguenth at gcc dot gnu.org 2013-11-06 21:00 ` eugeni.stepanov at gmail dot com 2013-11-11 21:09 ` mikpelinux at gmail dot com 2013-11-12 17:32 ` meissner at gcc dot gnu.org [this message] 2013-11-12 17:37 ` kcc at gcc dot gnu.org 2013-11-12 22:01 ` mikpelinux at gmail dot com 2013-11-13 6:03 ` kcc at gcc dot gnu.org 2013-11-13 17:06 ` bergner at gcc dot gnu.org 2013-11-13 17:14 ` meissner at linux dot vnet.ibm.com 2013-11-13 17:23 ` jakub at gcc dot gnu.org 2013-11-13 17:28 ` kcc at gcc dot gnu.org 2013-11-13 22:34 ` bergner at gcc dot gnu.org 2013-11-14 5:05 ` dave.anglin at bell dot net 2013-11-14 15:24 ` bergner at gcc dot gnu.org 2013-11-14 17:27 ` bergner at gcc dot gnu.org 2013-11-14 18:04 ` dave.anglin at bell dot net 2013-11-14 18:15 ` bergner at gcc dot gnu.org 2013-11-14 18:24 ` jakub at gcc dot gnu.org 2013-11-15 3:25 ` dave.anglin at bell dot net 2013-12-08 17:14 ` danglin at gcc dot gnu.org 2013-12-09 13:01 ` kcc at gcc dot gnu.org 2013-12-09 13:10 ` dominiq at lps dot ens.fr 2013-12-09 13:33 ` kcc at gcc dot gnu.org 2013-12-09 17:14 ` dominiq at lps dot ens.fr 2013-12-10 16:46 ` danglin at gcc dot gnu.org 2013-12-10 16:49 ` jakub at gcc dot gnu.org 2013-12-10 17:46 ` dominiq at lps dot ens.fr 2013-12-10 18:21 ` dave.anglin at bell dot net 2013-12-19 9:30 ` dominiq at lps dot ens.fr 2013-12-19 9:31 ` kcc at gcc dot gnu.org 2013-12-19 9:34 ` dominiq at lps dot ens.fr 2013-12-19 9:40 ` kcc at gcc dot gnu.org 2013-12-19 10:09 ` dominiq at lps dot ens.fr 2013-12-19 12:54 ` kcc at gcc dot gnu.org 2013-12-19 22:36 ` dominiq at lps dot ens.fr 2013-12-19 22:53 ` dave.anglin at bell dot net 2013-12-20 17:36 ` dave.anglin at bell dot net 2014-04-22 11:38 ` jakub at gcc dot gnu.org 2014-07-16 13:31 ` jakub at gcc dot gnu.org 2014-10-19 22:11 ` sandra at codesourcery dot com 2014-10-19 22:20 ` pinskia at gcc dot gnu.org 2014-10-30 10:42 ` jakub at gcc dot gnu.org 2014-12-10 10:16 ` jiwang at gcc dot gnu.org 2014-12-10 10:51 ` [Bug sanitizer/59009] libsanitizer merge from upstream r191666 breaks bootstrap on powerpc64-linux and aarch64-linux jiwang at gcc dot gnu.org 2015-02-04 12:58 ` mkuvyrkov at gcc dot gnu.org 2015-02-04 12:59 ` mkuvyrkov at gcc dot gnu.org 2015-02-04 17:40 ` clyon at gcc dot gnu.org 2015-02-05 17:19 ` clyon at gcc dot gnu.org 2015-02-07 21:43 ` clyon at gcc dot gnu.org 2015-02-25 10:36 ` clyon at gcc dot gnu.org 2015-03-03 21:23 ` clyon at gcc dot gnu.org 2015-03-03 21:24 ` clyon at gcc dot gnu.org 2015-03-23 14:05 ` clyon at gcc dot gnu.org 2015-03-23 14:06 ` clyon at gcc dot gnu.org 2015-06-26 20:02 ` jakub at gcc dot gnu.org 2015-06-26 20:32 ` 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-59009-4-LJpgqbyIW5@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).