public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/91459] Tail-Call Optimization is not performed when return value is assumed. Date: Mon, 27 Dec 2021 06:00:31 +0000 [thread overview] Message-ID: <bug-91459-4-u53zSFyFXZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-91459-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91459 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed|2019-08-16 00:00:00 |2021-12-26 --- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> --- So when DOM3 changes: result_5 = function_returns_only_1_or_doesnt_return (a_2(D), b_3(D)); if (result_5 == 1) goto <bb 3>; [100.00%] else goto <bb 4>; [0.00%] <bb 3> [local count: 1073741824]: return 1; <bb 4> [count: 0]: __builtin_unreachable (); To result_5 = function_returns_only_1_or_doesnt_return (a_2(D), b_3(D)); return 1; I wonder if it could change 1 back into result_5 because it comes from a function call.
parent reply other threads:[~2021-12-27 6:00 UTC|newest] Thread overview: expand[flat|nested] mbox.gz Atom feed [parent not found: <bug-91459-4@http.gcc.gnu.org/bugzilla/>]
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-91459-4-u53zSFyFXZ@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).