public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dje at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/51982] New: Shrink-wrapping opportunity Date: Tue, 24 Jan 2012 19:08:00 -0000 [thread overview] Message-ID: <bug-51982-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51982 Bug #: 51982 Summary: Shrink-wrapping opportunity Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: middle-end AssignedTo: unassigned@gcc.gnu.org ReportedBy: dje@gcc.gnu.org Created attachment 26444 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26444 lookdict_string manually split equivalent to shrink-wrapping I realize that the shrink-wrapping implementation in GCC is preliminary and conservative. I tested it on an example that presents a good opportunity for shrink-wrapping and a large perforamnce improvement, but the current implementation was not able to apply the optimization. The attached file manually splits the CPython lookdict_string() into two functions where most of the prologue can be avoided on the slow path.
next reply other threads:[~2012-01-24 18:48 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-24 19:08 dje at gcc dot gnu.org [this message] 2012-01-24 19:42 ` [Bug middle-end/51982] " pinskia at gcc dot gnu.org 2012-01-24 19:42 ` dje at gcc dot gnu.org 2012-02-06 7:07 ` amodra at gmail dot com 2013-04-21 23:26 ` dje at gcc dot gnu.org 2013-11-25 13:10 ` jamborm at gcc dot gnu.org 2021-12-25 11:32 ` [Bug rtl-optimization/51982] " 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-51982-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).