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/96370] [8/9 Regression] ICE with -ffast-math since r7-950-g8a85cee26eabf5cf Date: Wed, 02 Dec 2020 12:21:16 +0000 [thread overview] Message-ID: <bug-96370-4-gA0IGZfyH0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96370-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96370 --- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-9 branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:a5fff78405c3bfea287434e7711c6f10a770cb0a commit r9-9087-ga5fff78405c3bfea287434e7711c6f10a770cb0a Author: Richard Biener <rguenther@suse.de> Date: Thu Jul 30 10:24:42 2020 +0200 tree-optimization/96370 - make reassoc expr rewrite more robust In the face of the more complex tricks in reassoc with respect to negate processing it can happen that the expression rewrite is fooled to recurse on a leaf and pick up a bogus expression code. The following patch makes the expression rewrite more robust in providing the expression code to it directly since it is the same for all operations in a chain. 2020-07-30 Richard Biener <rguenther@suse.de> PR tree-optimization/96370 * tree-ssa-reassoc.c (rewrite_expr_tree): Add operation code parameter and use it instead of picking it up from the stmt that is being rewritten. (reassociate_bb): Pass down the operation code. * gcc.dg/pr96370.c: New testcase. (cherry picked from commit 2c558d2655cb22f472c83e8296b5cd2a92365cd3)
next prev parent reply other threads:[~2020-12-02 12:21 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-29 14:23 [Bug c/96370] New: ice with -ffast-math dcb314 at hotmail dot com 2020-07-30 6:00 ` [Bug tree-optimization/96370] " rguenth at gcc dot gnu.org 2020-07-30 7:28 ` marxin at gcc dot gnu.org 2020-07-30 7:35 ` [Bug tree-optimization/96370] ICE with -ffast-math since r7-950-g8a85cee26eabf5cf marxin at gcc dot gnu.org 2020-07-30 8:02 ` rguenth at gcc dot gnu.org 2020-07-30 8:15 ` rguenth at gcc dot gnu.org 2020-07-30 9:36 ` cvs-commit at gcc dot gnu.org 2020-07-30 9:46 ` [Bug tree-optimization/96370] [8/9/10 Regression] " rguenth at gcc dot gnu.org 2020-09-11 12:12 ` cvs-commit at gcc dot gnu.org 2020-12-02 12:21 ` cvs-commit at gcc dot gnu.org [this message] 2021-03-17 11:14 ` [Bug tree-optimization/96370] [8 " cvs-commit at gcc dot gnu.org 2021-03-17 11:15 ` 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-96370-4-gA0IGZfyH0@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).