public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <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 17:56:02 +0000	[thread overview]
Message-ID: <bug-105376-4-w5P6HGpRQ9@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

--- Comment #3 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
For this transformation to be correct for DFP, you need a 2 with quantum 
exponent 0.  Converting from either integer or binary floating-point 2 
will work for that.  However, I note that decimal_to_decnumber has

    case rvc_normal:
      if (!r->decimal)
        {
          /* dconst{1,2,m1,half} are used in various places in
             the middle-end and optimizers, allow them here
             as an exception by converting them to decimal.  */

so the existing code ought to work as-is.  Maybe there is a problem with 
padding in REAL_VALUE_TYPE meaning the comparisons don't work as intended?

  parent reply	other threads:[~2022-04-26 17:56 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
2022-04-26 17:56 ` joseph at codesourcery dot com [this message]
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-w5P6HGpRQ9@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).