From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: 22337-done@debbugs.gnu.org, Andreas Metzler <ametzler@bebt.de>
Subject: bug#22337: Breakage on amd64 when built with -O1 and higher
Date: Tue, 28 Feb 2017 15:45:24 +0100 [thread overview]
Message-ID: <8760juml17.fsf@pobox.com> (raw)
In-Reply-To: <87wpjsq11b.fsf@pobox.com> (Andy Wingo's message of "Sun, 07 Aug 2016 13:19:28 +0200")
On Sun 07 Aug 2016 13:19, Andy Wingo <wingo@pobox.com> writes:
> On Sat 09 Jan 2016 15:57, ludo@gnu.org (Ludovic Courtès) writes:
>
>> 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.)
>
> Apparently this is still an issue. Debian actually reverted to
> compiling Guile with -O0:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809608
>
> Which is terrible of course. Surely it is a bug in the Guile GnuTLS
> bindings and not in Guile proper. Compiling Guile with -O2 probably
> holds on to less garbage; could it be that GnuTLS is erroneously not
> making its data structures visible?
From what I can tell, Debian is back to building Guile with -g -O2:
https://buildd.debian.org/status/fetch.php?pkg=guile-2.0&arch=i386&ver=2.0.13%2B1-4&stamp=1481333071&raw=0
Therefore marking this as closed.
Andy
next prev parent reply other threads:[~2017-02-28 14:45 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
2016-01-09 15:45 ` Andreas Metzler
2016-08-07 11:19 ` Andy Wingo
2017-02-28 14:45 ` Andy Wingo [this message]
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=8760juml17.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=22337-done@debbugs.gnu.org \
--cc=ametzler@bebt.de \
--cc=ludo@gnu.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.
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).