public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "stefanrin at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/99531] New: Performance regression since gcc 9 (argument passing / register allocation) Date: Wed, 10 Mar 2021 22:36:26 +0000 [thread overview] Message-ID: <bug-99531-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99531 Bug ID: 99531 Summary: Performance regression since gcc 9 (argument passing / register allocation) Product: gcc Version: 10.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: stefanrin at gmail dot com Target Milestone: --- Target: x86_64 For this source: int func(int, int, int, int, int, int); int caller(int a, int b, int c, int d, int e) { return func(0, a, b, c, d, e); } the code generated for caller is: pushq %r12 movl %r8d, %r9d popq %r12 movl %ecx, %r8d movl %edx, %ecx movl %esi, %edx movl %edi, %esi xorl %edi, %edi jmp func gcc 9 started producing the useless push/pop pair. Mailing list link: https://gcc.gnu.org/pipermail/gcc-help/2021-February/139885.html
next reply other threads:[~2021-03-10 22:36 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-10 22:36 stefanrin at gmail dot com [this message] 2021-03-11 8:32 ` [Bug target/99531] " rguenth at gcc dot gnu.org 2021-03-11 8:32 ` [Bug target/99531] [9/10/11 Regression] " rguenth at gcc dot gnu.org 2021-03-11 9:35 ` marxin at gcc dot gnu.org 2021-04-08 13:05 ` rguenth at gcc dot gnu.org 2021-06-01 8:19 ` [Bug target/99531] [9/10/11/12 " rguenth at gcc dot gnu.org 2021-12-07 13:48 ` vmakarov at gcc dot gnu.org 2021-12-13 19:11 ` cvs-commit at gcc dot gnu.org 2021-12-14 15:04 ` cvs-commit at gcc dot gnu.org 2022-05-27 9:44 ` [Bug target/99531] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:43 ` jakub at gcc dot gnu.org 2023-01-12 23:36 ` [Bug target/99531] [10/11 " roger at nextmovesoftware dot com 2023-07-07 10:39 ` [Bug target/99531] [11 " rguenth at gcc dot gnu.org 2024-05-20 23:14 ` olegendo at gcc dot gnu.org 2024-05-22 0:05 ` olegendo 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-99531-4@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).