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/90706] [10/11/12/13 Regression] Useless code generated for stack / register operations on AVR Date: Thu, 15 Dec 2022 19:20:06 +0000 [thread overview] Message-ID: <bug-90706-4-AiZlmNFSD2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-90706-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90706 --- Comment #15 from CVS 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:12abd5a7d13209f79664ea603b3f3517f71b8c4f commit r13-4727-g12abd5a7d13209f79664ea603b3f3517f71b8c4f Author: Vladimir N. Makarov <vmakarov@redhat.com> Date: Thu Dec 15 14:11:05 2022 -0500 IRA: Check that reg classes contain a hard reg of given mode in reg move cost calculation IRA calculates wrong AVR costs for moving general hard regs of SFmode. To calculate the costs we did not exclude sub-classes which do not contain hard regs of given mode. This was the reason for spilling a pseudo in the PR. The patch fixes this. PR rtl-optimization/90706 gcc/ChangeLog: * ira-costs.cc: Include print-rtl.h. (record_reg_classes, scan_one_insn): Add code to print debug info. * ira.cc (ira_init_register_move_cost): Check that at least one hard reg of the mode are in the class contents to calculate the register move costs. gcc/testsuite/ChangeLog: * gcc.target/avr/pr90706.c: New.
next prev parent reply other threads:[~2022-12-15 19:20 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-90706-4@http.gcc.gnu.org/bugzilla/> 2020-03-12 11:59 ` [Bug rtl-optimization/90706] [9/10 " jakub at gcc dot gnu.org 2020-03-13 23:25 ` bseifert at gmx dot at 2020-04-29 16:50 ` gjl at gcc dot gnu.org 2021-06-01 8:14 ` [Bug rtl-optimization/90706] [9/10/11/12 " rguenth at gcc dot gnu.org 2022-05-27 9:40 ` [Bug rtl-optimization/90706] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:37 ` jakub at gcc dot gnu.org 2022-11-01 15:55 ` gjl at gcc dot gnu.org 2022-12-13 14:10 ` vmakarov at gcc dot gnu.org 2022-12-15 19:20 ` cvs-commit at gcc dot gnu.org [this message] 2022-12-16 13:59 ` gjl at gcc dot gnu.org 2022-12-16 18:33 ` vmakarov at gcc dot gnu.org 2023-03-02 22:22 ` cvs-commit at gcc dot gnu.org 2023-03-04 13:45 ` gjl at gcc dot gnu.org 2023-03-31 12:42 ` cvs-commit at gcc dot gnu.org 2023-03-31 12:45 ` vmakarov at gcc dot gnu.org 2023-03-31 14:38 ` gjl at gcc dot gnu.org 2023-05-21 15:25 ` gjl at gcc dot gnu.org 2024-03-05 19:28 ` gjl at gcc dot gnu.org 2024-05-18 8:15 ` gjl 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-90706-4-AiZlmNFSD2@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).