unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Cyprien Nicolas <cyprien@nicolas.tf>
Cc: 36338@debbugs.gnu.org
Subject: bug#36338: guile-2.2.5 fails to build with -ffast-math
Date: Wed, 26 Jun 2019 22:57:57 -0400	[thread overview]
Message-ID: <87lfxnrayy.fsf@netris.org> (raw)
In-Reply-To: <c706f0a4-a2ac-87be-baa5-9991a6526e66@nicolas.tf> (Cyprien Nicolas's message of "Sun, 23 Jun 2019 11:00:23 +0200")

tags 36338 + notabug wontfix
close 36338
thanks

Hi Cyprien,

Cyprien Nicolas <cyprien@nicolas.tf> writes:

> I apologize if the issue was already reported, but I didn't find a
> previous record.
>
> At Gentoo, users build packages themselves, and have the freedom to
> choose the CFLAGS they want.
>
> We had several reports [1,2] from users unable to build guile with
> -Ofast. Adding -fno-fast-math make the build pass.
>
> Compiling with -O0 -ffast-math also fails.

Guile generally assumes that the underlying C implementation will be
standards compliant.  -Ofast, -ffast-math and related options disregard
standards compliance.  Among other things, -ffast-math implies
-ffinite-math-only, which generates code that assumes that all floating
point values are finite.  However, there's code in Guile's compiler that
uses +inf.0 and -inf.0 and expects that they will behave as specified in
IEEE-754.

So, in summary, I would say that Guile does not support being compiled
with -Ofast, -ffast-math, or many of the options that -ffast-math
implies.

> I'm not sure if you can solve this. On our side, we will append
> -fno-fast-math to compiler's flags.

I think this is the right approach.

     Thanks,
       Mark





  reply	other threads:[~2019-06-27  2:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-23  9:00 bug#36338: guile-2.2.5 fails to build with -ffast-math Cyprien Nicolas
2019-06-27  2:57 ` Mark H Weaver [this message]
2019-07-07 13:03   ` Cyprien Nicolas

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=87lfxnrayy.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=36338@debbugs.gnu.org \
    --cc=cyprien@nicolas.tf \
    /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).