public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/107299] [13 regression] ICE in stage 1 after r13-3307-g8efc38347a7444
Date: Tue, 18 Oct 2022 07:08:20 +0000 [thread overview]
Message-ID: <bug-107299-4-tMLvreqTC9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107299-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107299
--- Comment #4 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
(In reply to Aldy Hernandez from comment #3)
> We are failing while trying to fold:
>
> c_92 = __builtin_copysignf128 (0.0, c_80(D));
>
> The problem is that c_92 is TFtype but 0.0 is _Float128. TFtype has a
> precision of 127 whereas _Float128 has a precision of 128. This causes the
> assert in fold_using_range::fold_stmt to fail because range_compatible_p is
> false.
>
> Are both operands of copysign allowed to have different types / precisions?
Sorry, what I meant to say is that c_92 is TFtype, whereas
__builtin_copysignf128 is assuming to return the type of the first operand
(0.0, which is _Float128). Is this correct?
next prev parent reply other threads:[~2022-10-18 7:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 21:16 [Bug other/107299] New: [13 regression] seurer at gcc dot gnu.org
2022-10-18 5:43 ` [Bug bootstrap/107299] [13 regression] ICE in stage 1 after r13-3307-g8efc38347a7444 aldyh at gcc dot gnu.org
2022-10-18 5:52 ` linkw at gcc dot gnu.org
2022-10-18 7:01 ` aldyh at gcc dot gnu.org
2022-10-18 7:08 ` aldyh at gcc dot gnu.org [this message]
2022-10-18 7:26 ` rguenth at gcc dot gnu.org
2022-10-18 7:27 ` rguenth at gcc dot gnu.org
2022-10-18 7:27 ` rguenth at gcc dot gnu.org
2022-10-18 10:13 ` aldyh at gcc dot gnu.org
2022-10-18 10:16 ` aldyh at gcc dot gnu.org
2022-10-26 17:46 ` seurer at gcc dot gnu.org
2023-03-06 22:42 ` cvs-commit at gcc dot gnu.org
2023-03-09 15:10 ` redi at gcc dot gnu.org
2023-03-15 9:40 ` rguenth 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-107299-4-tMLvreqTC9@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).