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 10:16:37 +0000 [thread overview]
Message-ID: <bug-107299-4-PKZoRzdQJp@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 #7 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
It looks like the 0.0 with the wrong type is there quite early in the pipeline.
At least by einline (after SSA and CFG have been built) we have:
(gdb) p debug(gs)
c_92 = __builtin_copysignf128 (0.0, c_80(D));
c_92 has a type of TFtype:
(gdb) p debug_tree(lhs)
<ssa_name 0x7fffef2d23b8
type <real_type 0x7fffef5211b8 TFtype sizes-gimplified TF
size <integer_cst 0x7fffef221038 constant 128>
unit-size <integer_cst 0x7fffef221050 constant 16>
align:128 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type
0x7fffef251500 precision:127 context <translation_unit_decl 0x7fffef510960
a.i>>
visited var <parm_decl 0x7ffff7f84f80 c>
def_stmt 163c_92 = __builtin_copysignf128 (0.0, c_80(D));
version:92>
$12 = void
Whereas 0.0 has a type of _Float128:
(gdb) p gimple_call_arg (gs, 0)
$13 = (tree_node *) 0x7fffef54d1a0
(gdb) p debug($13)
0.0
$14 = void
(gdb) p debug_tree($13)
<real_cst 0x7fffef54d1a0
type <real_type 0x7fffef2516f8 _Float128 TF
size <integer_cst 0x7fffef221038 constant 128>
unit-size <integer_cst 0x7fffef221050 constant 16>
align:128 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type
0x7fffef2516f8 precision:128>
constant 0.0>
next prev parent reply other threads:[~2022-10-18 10:16 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
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 [this message]
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-PKZoRzdQJp@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).