public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/43920] Choosing conditional execution over conditional branches for code size in some cases. Date: Tue, 05 Apr 2011 10:13:00 -0000 [thread overview] Message-ID: <bug-43920-4-PK0WGlSiHH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-43920-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43920 --- Comment #6 from vries at gcc dot gnu.org 2011-04-05 10:12:17 UTC --- Author: vries Date: Tue Apr 5 10:12:14 2011 New Revision: 171977 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=171977 Log: 2011-04-05 Tom de Vries <tom@codesourcery.com> PR target/43920 * function.c (emit_use_return_register_into_block): New function. (thread_prologue_and_epilogue_insns): Use emit_use_return_register_into_block. Modified: trunk/gcc/ChangeLog trunk/gcc/function.c
next prev parent reply other threads:[~2011-04-05 10:13 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-43920-4@http.gcc.gnu.org/bugzilla/> 2011-04-05 10:05 ` vries at gcc dot gnu.org 2011-04-05 10:13 ` vries at gcc dot gnu.org [this message] 2011-04-05 10:34 ` vries at gcc dot gnu.org 2011-04-05 13:02 ` vries at gcc dot gnu.org 2011-04-06 9:41 ` ramana at gcc dot gnu.org 2011-04-07 8:10 ` vries at gcc dot gnu.org 2011-04-07 8:35 ` vries at gcc dot gnu.org 2011-04-07 9:28 ` vries at gcc dot gnu.org 2011-04-07 9:48 ` vries at gcc dot gnu.org 2011-07-11 16:38 ` vries at gcc dot gnu.org 2011-09-19 6:21 ` jye2 at gcc dot gnu.org 2010-04-28 8:18 [Bug target/43920] New: A lot of instructions for condition (start == -1 || end == -1) carrot at google dot com 2010-04-28 9:55 ` [Bug target/43920] Choosing conditional execution over conditional branches for code size in some cases ramana at gcc dot gnu dot org 2010-04-29 2:24 ` carrot at google 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-43920-4-PK0WGlSiHH@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).