From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Metzler <ametzler@bebt.de>
Cc: 22337@debbugs.gnu.org
Subject: bug#22337: Breakage on amd64 when built with -O1 and higher
Date: Sat, 09 Jan 2016 15:57:38 +0100 [thread overview]
Message-ID: <877fjidcm5.fsf@gnu.org> (raw)
In-Reply-To: <20160109134721.GD1241@argenau.bebt.de> (Andreas Metzler's message of "Sat, 9 Jan 2016 14:47:21 +0100")
Andreas Metzler <ametzler@bebt.de> skribis:
> Debian used to build guile-2.0 without optimization, after changing to
> -O2 random segfaults in guile-gnutls testsuite started to appear on
> amd64.
Are you sure the GnuTLS issue has anything to do with that?
Guile has always been built with ‘-O2 -g’ by default, and building with
‘-O0’ has never really been supported (the VM engine could eat too much
stack space and do silly things.)
Ludo’.
next prev parent reply other threads:[~2016-01-09 14:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-09 13:47 bug#22337: Breakage on amd64 when built with -O1 and higher Andreas Metzler
2016-01-09 14:57 ` Ludovic Courtès [this message]
2016-01-09 15:45 ` Andreas Metzler
2016-08-07 11:19 ` Andy Wingo
2017-02-28 14:45 ` Andy Wingo
2017-02-28 16:37 ` Andreas Metzler
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877fjidcm5.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=22337@debbugs.gnu.org \
--cc=ametzler@bebt.de \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).