From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 2DCE41A1F32 for ; Wed, 21 Sep 2016 20:40:38 -0700 (PDT) Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id ABDB8C04B944; Thu, 22 Sep 2016 03:40:37 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-116-25.phx2.redhat.com [10.3.116.25]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u8M3earc025438; Wed, 21 Sep 2016 23:40:36 -0400 To: Bruce Cran , edk2-devel@ml01.01.org References: <37fea717-e59b-d20b-8223-54ed6caa215d@cran.org.uk> Cc: Ard Biesheuvel From: Laszlo Ersek Message-ID: <9d78e357-1490-3760-c165-85c5242bf7de@redhat.com> Date: Thu, 22 Sep 2016 05:40:35 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <37fea717-e59b-d20b-8223-54ed6caa215d@cran.org.uk> X-Scanned-By: MIMEDefang 2.68 on 10.5.11.24 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.31]); Thu, 22 Sep 2016 03:40:37 +0000 (UTC) Subject: Re: NOOPT OVMF build (or otherwise with optimizations disabled) X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2016 03:40:38 -0000 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit On 09/22/16 05:02, Bruce Cran wrote: > Would it be possible to either have a NOOPT build for OVMF added, or > have the DEBUG build disable optimizations? Personally I'd expect > debug builds in general to disable optimizations to allow easy > source-level debugging, but it seems the decision has been made to keep > optimizations enabled for EDK2 and have a NOOPT configuration for > debugging? Yes, I seem to recall that DEBUG means optimizations enabled, but debug code (such as DEBUG(), ASSERT(), DEBUG_CODE(...), ASSERT_EFI_ERROR()) included. Indeed NOOPT seems to be what edk2 assigns generally to the build you'd like. A NOOPT build target for OVMF (and more generally for GCC toolchains I guess?) should be possible, likely even welcome, I believe. If only someone contributed such BaseTools patches. :) ('git grep -e NOOPT --and -e GCC -- BaseTools' returns no hits.) Thanks Laszlo