public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/10474] shrink wrapping for functions Date: Wed, 17 Apr 2013 15:52:00 -0000 [thread overview] Message-ID: <bug-10474-4-SveFCA7INE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-10474-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10474 Martin Jambor <jamborm at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jamborm at gcc dot gnu.org Component|tree-optimization |middle-end --- Comment #11 from Martin Jambor <jamborm at gcc dot gnu.org> 2013-04-17 15:52:44 UTC --- I've submitted a patch that actually makes shrink wrapping happen, at least on x86_64. It would be great if someone checked whether it helps on other platforms: http://gcc.gnu.org/ml/gcc-patches/2013-04/msg01033.html (I'm also changing the component to to middle end as this is hardly a tree-optimization matter.)
next prev parent reply other threads:[~2013-04-17 15:52 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-10474-4@http.gcc.gnu.org/bugzilla/> 2011-05-18 5:32 ` [Bug tree-optimization/10474] gcc should be able to delay the setup of the frame pointer (patrial outlining) pinskia at gcc dot gnu.org 2011-12-02 2:47 ` pinskia at gcc dot gnu.org 2013-04-17 15:52 ` jamborm at gcc dot gnu.org [this message] 2013-10-29 14:51 ` [Bug rtl-optimization/10474] shrink wrapping for functions jamborm at gcc dot gnu.org 2013-10-30 12:01 ` jamborm at gcc dot gnu.org 2013-11-12 12:54 ` jamborm at gcc dot gnu.org 2013-11-22 19:37 ` law at gcc dot gnu.org 2013-11-25 13:10 ` jamborm at gcc dot gnu.org 2013-11-25 14:19 ` scovich at gmail dot com 2013-11-25 14:57 ` jamborm at gcc dot gnu.org 2013-11-25 15:43 ` scovich at gmail dot com
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-10474-4-SveFCA7INE@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).