public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "slyfox at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/106831] New: [13 Regression] mpfr-4.1.0 started failing 2 tests: tget_set_d64 and tget_set_d128
Date: Mon, 05 Sep 2022 07:18:31 +0000 [thread overview]
Message-ID: <bug-106831-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106831
Bug ID: 106831
Summary: [13 Regression] mpfr-4.1.0 started failing 2 tests:
tget_set_d64 and tget_set_d128
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: slyfox at gcc dot gnu.org
Target Milestone: ---
The test failures came up on this week's gcc snapshot updates:
- works: gcc-13.0.0.20220828 -O2
- fails: gcc-13.0.0.20220904 -O2
- works: gcc-13.0.0.20220904 -O0
Against https://ftp.gnu.org/gnu/mpfr/mpfr-4.1.0.tar.xz the following seems to
be enough:
$ ./configure CC=gcc-13 && make && make check
Did not extract details yet to double-check if it's really a compiler error
(and not an mpfr deficiency). But -O0 / -O2 difference might be a hint.
Two test failures reported:
FAIL: tget_set_d64
==================
Error in check_misc for +0.
mpfr_get_decimal64() returned:
|1011000110100000000000000000000000000000000000000000000000000000|
mpfr_set_decimal64() set x to: -0 approx.
= -0
FAIL tget_set_d64 (exit status: 1)
FAIL: tget_set_d128
===================
Error in check_misc for +0.
mpfr_get_decimal128() returned: 0.0
mpfr_set_decimal128() set x to: -0 approx.
= -0
FAIL tget_set_d128 (exit status: 1)
$ gcc -v
Using built-in specs.
COLLECT_GCC=/<<NIX>>/gcc-13.0.0/bin/gcc
COLLECT_LTO_WRAPPER=/<<NIX>>/gcc-13.0.0/libexec/gcc/x86_64-unknown-linux-gnu/13.0.0/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with:
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 13.0.0 20220904 (experimental) (GCC)
next reply other threads:[~2022-09-05 7:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 7:18 slyfox at gcc dot gnu.org [this message]
2022-09-05 7:55 ` [Bug target/106831] " jakub at gcc dot gnu.org
2022-09-05 8:02 ` aldyh at gcc dot gnu.org
2022-09-05 8:04 ` aldyh at gcc dot gnu.org
2022-09-05 12:05 ` slyfox at gcc dot gnu.org
2022-09-05 12:57 ` aldyh at gcc dot gnu.org
2022-09-05 13:05 ` jakub at gcc dot gnu.org
2022-09-05 13:35 ` aldyh at gcc dot gnu.org
2022-09-05 13:48 ` [Bug middle-end/106831] " jakub at gcc dot gnu.org
2022-09-05 13:54 ` aldyh at gcc dot gnu.org
2022-09-05 14:56 ` jakub at gcc dot gnu.org
2022-09-05 15:57 ` cvs-commit at gcc dot gnu.org
2022-09-05 15:59 ` aldyh at gcc dot gnu.org
2022-09-05 19:32 ` joseph at codesourcery dot com
2022-09-18 7:04 ` cvs-commit at gcc dot gnu.org
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-106831-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.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).