public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/105376] ICE: in decimal_to_decnumber, at dfp.cc:134 with _Decimal128 at -O -g Date: Tue, 26 Apr 2022 06:48:10 +0000 [thread overview] Message-ID: <bug-105376-4-hkfyGnp8JA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105376-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105376 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsm28 at gcc dot gnu.org, | |rguenth at gcc dot gnu.org --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- (gdb) p debug_rtx (rtl) (const_double:TD -2.0e+0 [-0x0.8p+2]) but CONST_DOUBLE_REAL_VALUE (rtl) has ->recimal == false, and that's true even on the tree level. Generated by /* Convert x+x into x*2. */ (simplify (plus @0 @0) (if (SCALAR_FLOAT_TYPE_P (type)) (mult @0 { build_real (type, dconst2); }) (if (INTEGRAL_TYPE_P (type)) (mult @0 { build_int_cst (type, 2); })))) where indeed the dconst2 is not decimal. I have no idea how to create a DFP constant, but I guess that in priciple (at least for dconst2), creating the constant with double_type_node and then fold-converting to type might work? It just looks like a bit much of work ... Joseph, do you have any insights here? The above is of course copied from fold-const.cc originally.
next prev parent reply other threads:[~2022-04-26 6:48 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-25 13:21 [Bug rtl-optimization/105376] New: " zsojka at seznam dot cz 2022-04-25 13:23 ` [Bug rtl-optimization/105376] " marxin at gcc dot gnu.org 2022-04-26 6:48 ` rguenth at gcc dot gnu.org [this message] 2022-04-26 17:56 ` joseph at codesourcery dot com 2022-04-27 6:27 ` rguenth at gcc dot gnu.org 2022-04-27 6:31 ` rguenth at gcc dot gnu.org 2022-04-29 6:17 ` cvs-commit at gcc dot gnu.org 2022-04-29 6:18 ` rguenth at gcc dot gnu.org 2022-05-06 10:30 ` cvs-commit at gcc dot gnu.org 2022-07-22 9:49 ` 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-105376-4-hkfyGnp8JA@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: linkBe 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).