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/114415] [13/14 Regression] wrong code with -Oz -fno-dce -fno-forward-propagate -flive-range-shrinkage -fweb since r13-1826 Date: Thu, 04 Apr 2024 20:07:23 +0000 [thread overview] Message-ID: <bug-114415-4-wu0PnqAxrB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114415-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114415 --- Comment #6 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Vladimir Makarov <vmakarov@gcc.gnu.org>: https://gcc.gnu.org/g:a24476422ba311b83737cf8bdc5892a7fc7514eb commit r14-9793-ga24476422ba311b83737cf8bdc5892a7fc7514eb Author: Vladimir N. Makarov <vmakarov@redhat.com> Date: Thu Apr 4 16:04:04 2024 -0400 [PR114415][scheduler]: Fixing wrong code generation For the test case, the insn scheduler (working for live range shrinkage) moves insns modifying stack memory before an insn reserving the stack memory. Comments in the patch contains more details about the problem and its solution. gcc/ChangeLog: PR rtl-optimization/114415 * sched-deps.cc (add_insn_mem_dependence): Add memory check for mem argument. (sched_analyze_1): Treat stack pointer modification as memory read. (sched_analyze_2, sched_analyze_insn): Add memory guard for processing pending_read_mems. * sched-int.h (deps_desc): Add comment to pending_read_mems. gcc/testsuite/ChangeLog: PR rtl-optimization/114415 * gcc.target/i386/pr114415.c: New test.
next prev parent reply other threads:[~2024-04-04 20:07 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-21 12:52 [Bug target/114415] New: wrong code with -Oz -fno-dce -fno-forward-propagate -flive-range-shrinkage -fweb zsojka at seznam dot cz 2024-03-25 14:43 ` [Bug target/114415] [13/14 Regression] wrong code with -Oz -fno-dce -fno-forward-propagate -flive-range-shrinkage -fweb since r13-1826 jakub at gcc dot gnu.org 2024-03-25 16:59 ` jakub at gcc dot gnu.org 2024-03-25 17:15 ` jakub at gcc dot gnu.org 2024-03-29 23:49 ` law at gcc dot gnu.org 2024-04-03 16:28 ` vmakarov at gcc dot gnu.org 2024-04-04 11:32 ` vmakarov at gcc dot gnu.org 2024-04-04 20:07 ` cvs-commit at gcc dot gnu.org [this message] 2024-04-05 4:10 ` [Bug rtl-optimization/114415] [13 " law at gcc dot gnu.org 2024-04-06 12:01 ` ebotcazou at gcc dot gnu.org 2024-04-06 17:35 ` law at gcc dot gnu.org 2024-05-08 12:28 ` rguenth at gcc dot gnu.org 2024-05-09 10:04 ` jakub at gcc dot gnu.org 2024-05-09 15:40 ` vmakarov at gcc dot gnu.org 2024-05-09 16:42 ` cvs-commit at gcc dot gnu.org 2024-05-09 19:06 ` 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-114415-4-wu0PnqAxrB@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).