From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28340 invoked by alias); 2 Jun 2016 13:35:17 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 38573 Received: (qmail 29458 invoked from network); 2 Jun 2016 13:35:14 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 Date: Thu, 02 Jun 2016 13:28:31 +0000 From: Daniel Shahaf To: Zsh hackers list Subject: Re: new zsh build hang on sparkylinux (essentially debian test) Message-ID: <20160602132831.GA15768@tarsus.local2> References: <160601180514.ZM13286@torch.brasslantern.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <160601180514.ZM13286@torch.brasslantern.com> User-Agent: Mutt/1.5.23 (2014-03-12) Bart Schaefer wrote on Wed, Jun 01, 2016 at 18:05:14 -0700: > Does our "configure" assure that the test cases are run with the same > compiler optimization flags as the final build? Datapoint: the zsh_cv_c_have_union_init AC_TRY_COMPILE() check happens before adding the output of `pcre-config --cflags` to CPPFLAGS. Cheers, Daniel (Bart: thanks for 38569; it'll take me more time to digest it) > Obviously compiler optimization isn't intended to change semantics, but > there may be some behavior that differs among standards and we're relying > on some variant that occurs when the build is not optimized.