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 middle-end/104522] ICE: in real_to_decimal_for_mode with -O -fdump-tree-all-details and long double
Date: Mon, 14 Feb 2022 14:27:26 +0000	[thread overview]
Message-ID: <bug-104522-4-ThujHkyFgE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104522-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104522

--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> ---
So my question is whether something should normalize those numbers and why
decode_ieee_extended happily initializes an invalid number (its documentation
of course might suggest it only expects valid encoded numbers).

But yes, enabling this re-interpretation checking unconditionally sounds like
the way to go.

  parent reply	other threads:[~2022-02-14 14:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-13 19:09 [Bug rtl-optimization/104522] New: ICE: in real_to_decimal_for_mode, at real.cc:1770 with -O -fcompare-debug zsojka at seznam dot cz
2022-02-13 22:09 ` [Bug middle-end/104522] " pinskia at gcc dot gnu.org
2022-02-13 22:13 ` [Bug middle-end/104522] ICE: in real_to_decimal_for_mode with -O -fdump-tree-all-details and long double pinskia at gcc dot gnu.org
2022-02-14  9:43 ` rguenth at gcc dot gnu.org
2022-02-14 10:06 ` rguenth at gcc dot gnu.org
2022-02-14 11:08 ` ubizjak at gmail dot com
2022-02-14 11:51 ` rguenth at gcc dot gnu.org
2022-02-14 11:51 ` rguenth at gcc dot gnu.org
2022-02-14 13:20 ` jakub at gcc dot gnu.org
2022-02-14 14:27 ` rguenth at gcc dot gnu.org [this message]
2022-02-14 15:47 ` jakub at gcc dot gnu.org
2022-02-15 11:12 ` 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-104522-4-ThujHkyFgE@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).