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 tree-optimization/98766] [10/11 Regression] SVE: ICE in tree_to_shwi with -O3 --param=avoid-fma-max-bits
Date: Fri, 22 Jan 2021 16:41:18 +0000	[thread overview]
Message-ID: <bug-98766-4-Ii8ek96PzD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98766-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Kyrylo Tkachov <ktkachov@gcc.gnu.org>:

https://gcc.gnu.org/g:9d33785f57daf29dc0c106c919da319fe1906bc6

commit r11-6861-g9d33785f57daf29dc0c106c919da319fe1906bc6
Author: Kyrylo Tkachov <kyrylo.tkachov@arm.com>
Date:   Thu Jan 21 16:33:49 2021 +0000

    tree-ssa-mathopts: Use proper poly_int64 comparison with
param_avoid_fma_max_bits [PR 98766]

    We ICE here because we end up comparing a poly_int64 with a scalar using
    <= rather than maybe_le.
    This patch fixes that in the way rich suggests in the PR.

    gcc/ChangeLog:

            PR tree-optimization/98766
            * tree-ssa-math-opts.c (convert_mult_to_fma): Use maybe_le when
            comparing against type size with param_avoid_fma_max_bits.

    gcc/testsuite/ChangeLog:

            PR tree-optimization/98766
            * gcc.dg/pr98766.c: New test.

  parent reply	other threads:[~2021-01-22 16:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-20 12:02 [Bug tree-optimization/98766] New: " acoplan at gcc dot gnu.org
2021-01-20 12:06 ` [Bug tree-optimization/98766] [10/11 Regression] " ktkachov at gcc dot gnu.org
2021-01-20 14:50 ` rguenth at gcc dot gnu.org
2021-01-22 12:41 ` ktkachov at gcc dot gnu.org
2021-01-22 16:41 ` cvs-commit at gcc dot gnu.org [this message]
2021-01-22 16:42 ` [Bug tree-optimization/98766] [10 " ktkachov at gcc dot gnu.org
2021-01-27 14:42 ` cvs-commit at gcc dot gnu.org
2021-01-27 14:44 ` ktkachov 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-98766-4-Ii8ek96PzD@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).