public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gabravier at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/95481] New: Failure to optimize infinite recursion for struct types Date: Tue, 02 Jun 2020 16:55:40 +0000 [thread overview] Message-ID: <bug-95481-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95481 Bug ID: 95481 Summary: Failure to optimize infinite recursion for struct types Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: gabravier at gmail dot com Target Milestone: --- struct A {}; struct A foo() { return foo(); } This can be optimized to an infinite loop. With -O3, GCC currently outputs an explicit recursive call like this : foo(): sub rsp, 8 call foo() xor eax, eax add rsp, 8 ret When it could just do this : foo(): .L2: jmp .L2
next reply other threads:[~2020-06-02 16:55 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-02 16:55 gabravier at gmail dot com [this message] 2020-06-02 17:07 ` [Bug middle-end/95481] " pinskia at gcc dot gnu.org 2021-05-30 22:45 ` [Bug tree-optimization/95481] Failure to optimize infinite recursion for empty " pinskia at gcc dot gnu.org 2021-05-31 0:21 ` pinskia at gcc dot gnu.org 2021-05-31 6:32 ` pinskia at gcc dot gnu.org 2021-06-01 18:29 ` cvs-commit at gcc dot gnu.org 2021-06-01 18:31 ` pinskia 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-95481-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).