From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18106 invoked by alias); 24 Aug 2012 09:13:58 -0000 Received: (qmail 18094 invoked by uid 22791); 24 Aug 2012 09:13:57 -0000 X-SWARE-Spam-Status: No, hits=-3.7 required=5.0 tests=BAYES_00,FREEMAIL_FROM,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_YE,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from qmta07.emeryville.ca.mail.comcast.net (HELO qmta07.emeryville.ca.mail.comcast.net) (76.96.30.64) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 24 Aug 2012 09:13:44 +0000 Received: from omta17.emeryville.ca.mail.comcast.net ([76.96.30.73]) by qmta07.emeryville.ca.mail.comcast.net with comcast id qZCm1j0011afHeLA7ZDkTQ; Fri, 24 Aug 2012 09:13:44 +0000 Received: from bag6-1-pt.tunnel.tserv3.fmt2.ipv6.he.net ([IPv6:2001:470:1f04:ae1::2]) by omta17.emeryville.ca.mail.comcast.net with comcast id qZDj1j0050P3DwE8dZDj5R; Fri, 24 Aug 2012 09:13:44 +0000 Subject: Re: Merge C++ conversion into trunk (0/6 - Overview) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Mike Stump In-Reply-To: <50372C39.9090204@gnu.org> Date: Fri, 24 Aug 2012 09:13:00 -0000 Cc: Diego Novillo , gcc-patches@gcc.gnu.org, Lawrence Crowl , dj@redhat.com, rguenther@suse.de, tromey@redhat.com, laurynas.biveinis@gmail.com Content-Transfer-Encoding: quoted-printable Message-Id: References: <20120812200427.GA12561@google.com> <7C104A77-8655-41DE-AF40-B1248B67D2E1@comcast.net> <50372C39.9090204@gnu.org> To: Paolo Bonzini X-IsSubscribed: yes Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org X-SW-Source: 2012-08/txt/msg01646.txt.bz2 On Aug 24, 2012, at 12:24 AM, Paolo Bonzini wrote: > Agreed, patch is preapproved. This is not really done to aid debugging > though, it is to avoid optimization bugs when compiling stage1. Ah, but building a non-bootstrap compiler from the top-level builds -O2 and= when built from the gcc subtree, builds -O0. Ever wonder why? It isn't t= o avoid code-gen errors in CC. it is to make the developers life easier. = I know, so much of gcc's history is lost to time and at times, not handed d= own to the new kids. The bad bits, just fade away. The useful things, for= example, this, will live on, as some of use still know about and use the f= eature. When it breaks, we complain.