From owner-freebsd-arch@FreeBSD.ORG Tue Oct 9 23:46:33 2007 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1349816A418 for ; Tue, 9 Oct 2007 23:46:33 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from mail11.syd.optusnet.com.au (mail11.syd.optusnet.com.au [211.29.132.192]) by mx1.freebsd.org (Postfix) with ESMTP id 8D31B13C457 for ; Tue, 9 Oct 2007 23:46:32 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from c220-239-235-248.carlnfd3.nsw.optusnet.com.au (c220-239-235-248.carlnfd3.nsw.optusnet.com.au [220.239.235.248]) by mail11.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id l99NkGGT000772 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 10 Oct 2007 09:46:21 +1000 Date: Wed, 10 Oct 2007 09:46:16 +1000 (EST) From: Bruce Evans X-X-Sender: bde@delplex.bde.org To: d@delphij.net In-Reply-To: <470AED31.60201@delphij.net> Message-ID: <20071010092255.O36751@delplex.bde.org> References: <470ACEA1.3030309@delphij.net> <20071009122751.X54949@besplex.bde.org> <470AED31.60201@delphij.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-arch@freebsd.org Subject: Re: Why we optimize by time by default for < -O2 case? X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Oct 2007 23:46:33 -0000 On Mon, 8 Oct 2007, LI Xin wrote: > Bruce Evans wrote: >>> Revision Changes Path >>> 1.15 +0 -0 src/contrib/gcc/toplev.c >> >> Without this change, -O pessimizes for time. > > Does this affect all platforms or is it i386 only, on the latest GCC > version? I don't know, but guess it affects some. In general, the pessimization works by breaking lookup of a table that gives the best alignment for the current target, so it affects all platforms that have such a table. On platforms with stricter alignment requirements than i386, gcc would have to adjust any -falign-foo settings that are too small to work. Then the pessimization might give minimal aligment != 1 and thus have no effect if the minimal alignment happens to equal the best alignment. Bruce