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/94873] [8/9/10/11 Regression] wrong code with -O -fno-merge-constants -fno-split-wide-types -fno-tree-fre Date: Wed, 06 May 2020 07:34:44 +0000 [thread overview] Message-ID: <bug-94873-4-0qCIyUb4Ai@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94873-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94873 --- Comment #20 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:f14848aea70066777faf201c0b6eb3c5520bfab9 commit r11-127-gf14848aea70066777faf201c0b6eb3c5520bfab9 Author: Jakub Jelinek <jakub@redhat.com> Date: Wed May 6 09:31:19 2020 +0200 combine: Don't replace SET_SRC with REG_EQUAL note content if SET_SRC has side-effects [PR94873] There were some discussions about whether REG_EQUAL notes are valid on insns with a single set which contains auto-inc-dec side-effects in the SET_SRC and the majority thinks that it should be valid. So, this patch fixes the combiner to punt in that case, because otherwise the auto-inc-dec side-effects from the SET_SRC are lost. 2020-05-06 Jakub Jelinek <jakub@redhat.com> PR rtl-optimization/94873 * combine.c (combine_instructions): Don't optimize using REG_EQUAL note if SET_SRC (set) has side-effects. * gcc.dg/pr94873.c: New test.
next prev parent reply other threads:[~2020-05-06 7:34 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-30 10:44 [Bug rtl-optimization/94873] New: [8/9/10 " zsojka at seznam dot cz 2020-04-30 12:36 ` [Bug rtl-optimization/94873] " jakub at gcc dot gnu.org 2020-04-30 12:42 ` jakub at gcc dot gnu.org 2020-04-30 12:46 ` jakub at gcc dot gnu.org 2020-04-30 15:00 ` jakub at gcc dot gnu.org 2020-05-01 15:11 ` [Bug rtl-optimization/94873] [8/9/10/11 " jakub at gcc dot gnu.org 2020-05-01 15:21 ` law at redhat dot com 2020-05-01 17:17 ` rsandifo at gcc dot gnu.org 2020-05-01 18:31 ` segher at gcc dot gnu.org 2020-05-01 18:52 ` rsandifo at gcc dot gnu.org 2020-05-04 19:09 ` segher at gcc dot gnu.org 2020-05-04 19:26 ` segher at gcc dot gnu.org 2020-05-04 19:58 ` rsandifo at gcc dot gnu.org 2020-05-04 20:47 ` rsandifo at gcc dot gnu.org 2020-05-04 22:12 ` ebotcazou at gcc dot gnu.org 2020-05-04 23:16 ` segher at gcc dot gnu.org 2020-05-05 7:24 ` ebotcazou at gcc dot gnu.org 2020-05-05 7:34 ` jakub at gcc dot gnu.org 2020-05-05 8:04 ` ebotcazou at gcc dot gnu.org 2020-05-05 10:22 ` jakub at gcc dot gnu.org 2020-05-05 15:02 ` segher at gcc dot gnu.org 2020-05-06 7:34 ` cvs-commit at gcc dot gnu.org [this message] 2020-05-06 11:50 ` [Bug rtl-optimization/94873] [8/9/10 " jakub at gcc dot gnu.org 2020-05-07 13:28 ` cvs-commit at gcc dot gnu.org 2020-05-07 13:33 ` [Bug rtl-optimization/94873] [8/9 " jakub at gcc dot gnu.org 2020-09-16 19:21 ` cvs-commit at gcc dot gnu.org 2020-09-17 17:49 ` jakub 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-94873-4-0qCIyUb4Ai@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).