public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit 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: Fri, 06 May 2022 10:30:02 +0000	[thread overview]
Message-ID: <bug-105376-4-lZYL4Q65D1@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 #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Richard Biener
<rguenth@gcc.gnu.org>:

https://gcc.gnu.org/g:39c56695c70a2052fc6bdcfca606dfff9c2fa975

commit r12-8348-g39c56695c70a2052fc6bdcfca606dfff9c2fa975
Author: Richard Biener <rguenther@suse.de>
Date:   Wed Apr 27 08:28:31 2022 +0200

    middle-end/105376 - invalid REAL_CST for DFP constant

    We are eventually ICEing in decimal_to_decnumber on non-decimal
    REAL_VALUE_TYPE that creep in from uses of build_real (..., dconst*)
    for DFP types.  The following extends the decimal_to_decnumber
    special-casing of dconst* to build_real, avoiding the bogus REAL_CSTs
    from creeping into the IL and modified to ones not handled by
    the decimal_to_decnumber special casing.  It also makes sure to
    ICE for not handled dconst* values at the point we build the REAL_CST.

    2022-04-27  Richard Biener  <rguenther@suse.de>

            PR middle-end/105376
            * tree.cc (build_real): Special case dconst* arguments
            for decimal floating point types.

            * gcc.dg/pr105376.c: New testcase.

    (cherry picked from commit e27eef7478f30ea79048dbde3317e89679d75a6e)

  parent reply	other threads:[~2022-05-06 10:30 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
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 [this message]
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-lZYL4Q65D1@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).