From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: Should we compile Guile with -fno-strict-aliasing?
Date: Sun, 29 Jan 2012 22:21:07 +0100 [thread overview]
Message-ID: <877h0anr24.fsf@gnu.org> (raw)
In-Reply-To: 87y5sssvu4.fsf@gnu.org
Hi!
ludo@gnu.org (Ludovic Courtès) skribis:
[...]
> I’ve just tried on this platform and it seems to fix the threading
> issues we were observing (though I won’t claim victory until Hydra
> reproduces the success several times in a row ;-)).
Well no, this one had nothing to do (see <http://bugs.gnu.org/10641>.)
> It may well be that my recent COMPILER_BARRIER hack can just go away
> with this.
I’ve verified and that asm volatile is not needed on sparc-linux-gnu and
hppa2.0-linux-gnu when compiling with -fno-strict-aliasing, so I’ve
reverted commit 2b264d7e4fb649955ade1814527b6eb6f34f4e18.
Thanks,
Ludo’.
next prev parent reply other threads:[~2012-01-29 21:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 19:02 Should we compile Guile with -fno-strict-aliasing? Mark H Weaver
2012-01-27 21:02 ` Ludovic Courtès
2012-01-29 21:21 ` Ludovic Courtès [this message]
2012-01-29 21:02 ` Andy Wingo
2012-01-29 21:10 ` Ludovic Courtès
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=877h0anr24.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@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).