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/99863] [10/11 Regression] wrong code with -O -fno-tree-forwprop -mno-sse2 since r10-7268-g529ea7d9596b26ba Date: Thu, 01 Apr 2021 10:47:06 +0000 [thread overview] Message-ID: <bug-99863-4-JndnBRocjn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99863-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99863 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:512429a885e87bef51057a001681b7d8d106e807 commit r11-7949-g512429a885e87bef51057a001681b7d8d106e807 Author: Richard Biener <rguenther@suse.de> Date: Thu Apr 1 11:51:33 2021 +0200 tree-optimization/99863 - clear vector CTOR TREE_SIDE_EFFECTS When we gimplify a vector CTOR the original CONSTRUCTOR tree remains but we fail to recompute flags such as TREE_SIDE_EFFECTS. This causes later GENERIC folding of them in vector lowering to give up since the match.pd machinery is careful about TREE_SIDE_EFFECTS. Fixing this makes vector lowering produce much less garbage and thus following the IL for PR99793 easier. 2021-04-01 Richard Biener <rguenther@suse.de> PR tree-optimization/99863 * gimplify.c (gimplify_init_constructor): Recompute vector constructor flags.
next prev parent reply other threads:[~2021-04-01 10:47 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-01 8:44 [Bug target/99863] New: [10/11 Regression] wrong code with -O -fno-tree-forwprop -mno-sse2 zsojka at seznam dot cz 2021-04-01 9:01 ` [Bug target/99863] " rguenth at gcc dot gnu.org 2021-04-01 9:14 ` rguenth at gcc dot gnu.org 2021-04-01 9:58 ` rguenth at gcc dot gnu.org 2021-04-01 10:02 ` [Bug target/99863] [10/11 Regression] wrong code with -O -fno-tree-forwprop -mno-sse2 since r10-7268-g529ea7d9596b26ba marxin at gcc dot gnu.org 2021-04-01 10:24 ` rguenth at gcc dot gnu.org 2021-04-01 10:45 ` [Bug rtl-optimization/99863] " rguenth at gcc dot gnu.org 2021-04-01 10:47 ` cvs-commit at gcc dot gnu.org [this message] 2021-04-01 11:16 ` ebotcazou at gcc dot gnu.org 2021-04-01 11:28 ` ebotcazou at gcc dot gnu.org 2021-04-01 12:26 ` jakub at gcc dot gnu.org 2021-04-01 12:45 ` rguenther at suse dot de 2021-04-01 13:01 ` jakub at gcc dot gnu.org 2021-04-01 13:23 ` jakub at gcc dot gnu.org 2021-04-01 13:27 ` jakub at gcc dot gnu.org 2021-04-01 13:32 ` rguenther at suse dot de 2021-04-01 13:35 ` jakub at gcc dot gnu.org 2021-04-01 13:54 ` jakub at gcc dot gnu.org 2021-04-03 8:07 ` cvs-commit at gcc dot gnu.org 2021-04-03 8:16 ` [Bug rtl-optimization/99863] [10 " jakub at gcc dot gnu.org 2021-04-08 12:02 ` rguenth at gcc dot gnu.org 2021-04-20 9:45 ` cvs-commit at gcc dot gnu.org 2021-04-20 9:50 ` jakub at gcc dot gnu.org 2021-04-20 23:34 ` cvs-commit at gcc dot gnu.org 2021-04-22 16:52 ` 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-99863-4-JndnBRocjn@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).