From: Maxime Devos <maximedevos@telenet.be>
To: Tomas Volf <~@wolfsden.cz>
Cc: guile-devel@gnu.org
Subject: Re: [PATCH] Add more detailed instructions into the HACKING file.
Date: Fri, 15 Dec 2023 23:16:29 +0100 [thread overview]
Message-ID: <4ba7b5de-5669-e173-1414-5c5a114efdf7@telenet.be> (raw)
In-Reply-To: <ZW5c725kXGBkLYvI@ws>
[-- Attachment #1.1.1: Type: text/plain, Size: 1386 bytes --]
Op 05-12-2023 om 00:12 schreef Tomas Volf:
> Thank you for the review.
>
> On 2023-12-04 22:06:42 +0100, Maxime Devos wrote:
>>
>>
>> Op 29-11-2023 om 17:40 schreef Tomas Volf:
>>> + guix shell -D -f guix.scm --pure -- ./configure --enable-mini-gmp
>>
>> Also -fexcess-precision=standard (see #49368 / #49659 on debbugs) (at least
>> for i*86, should be harmless for other architectures though).
>
> That explains why I did not catch it (I did run the test suite, but I am on
> x86_64).
I think it might, in theory, also happen on x86_64, and perhaps other
architectures with ‘excessive’ floats (I don't know any, but they could
exist).
If you encounter the issue or not depends on how, precisely, the
compiler optimises things, allocates registers/pushes things on the
stack ... you might have missed the issue by accident/luck.
> Out of curiosity, since it should be harmless elsewhere, is there a reason this
> is not a flag set by default?
I guess for compatible with non-GCC, non-Clang compilers.
But given how configure.ac now checks for support of '-flto', it should
be easy to copy/edit things to do the same for -fexcess-precision.
(Also, it is plausible that GCC simply does not recognise the flag on
non-i*86 and non-x86_64 architectures -- someone would need to actually
check this.)
Best regards,
Maxime Devos.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
prev parent reply other threads:[~2023-12-15 22:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 16:40 [PATCH] Add more detailed instructions into the HACKING file Tomas Volf
2023-12-04 21:06 ` Maxime Devos
2023-12-04 23:12 ` Tomas Volf
2023-12-15 22:16 ` Maxime Devos [this message]
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=4ba7b5de-5669-e173-1414-5c5a114efdf7@telenet.be \
--to=maximedevos@telenet.be \
--cc=guile-devel@gnu.org \
--cc=~@wolfsden.cz \
/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).