From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: new zsh build hang on sparkylinux (essentially debian test)
Date: Wed, 1 Jun 2016 18:05:14 -0700 [thread overview]
Message-ID: <160601180514.ZM13286@torch.brasslantern.com> (raw)
In-Reply-To: <CACeGjnXfvr0ktY40iODXXFDmyokXbwVXJOkKVeA-xZSpeCrCfw@mail.gmail.com>
Belated reply here, I've been traveling ... question directed at -workers,
not at Vin:
On May 13, 11:20pm, Vin Shelton wrote:
}
} Just for the record, this actually ended up being something to do with the
} compiler optimization settings. Building with CFLAGS=-O yielded a working
} zsh.
Does our "configure" assure that the test cases are run with the same
compiler optimization flags as the final build?
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.
next prev parent reply other threads:[~2016-06-02 1:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 1:08 Vin Shelton
2016-05-12 1:57 ` Bart Schaefer
2016-05-14 3:20 ` Vin Shelton
2016-06-02 1:05 ` Bart Schaefer [this message]
2016-06-02 13:28 ` Daniel Shahaf
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=160601180514.ZM13286@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).