public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "carrot at google dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/41653] not optimal result for multiplication with constant when -Os is specified Date: Thu, 15 Oct 2009 08:19:00 -0000 [thread overview] Message-ID: <20091015081858.2962.qmail@sourceware.org> (raw) In-Reply-To: <bug-41653-17659@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from carrot at google dot com 2009-10-15 08:18 ------- arm_size_rtx_costs calls thumb1_rtx_costs for TARGET_THUMB1. thumb1_rtx_costs is also called by several other functions. Looked at its implementation briefly, it is actually tuned for speed only. Following are some obvious example: case UDIV: case UMOD: case DIV: case MOD: return 100; case TRUNCATE: return 99; So a new function thumb1_size_rtx_costs is required to model the thumb1 size feature, right? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41653
next prev parent reply other threads:[~2009-10-15 8:19 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-10-10 9:20 [Bug target/41653] New: " carrot at google dot com 2009-10-12 21:51 ` [Bug target/41653] " rth at gcc dot gnu dot org 2009-10-15 8:19 ` carrot at google dot com [this message] 2009-10-15 10:19 ` ramana at gcc dot gnu dot org 2009-12-07 8:59 ` carrot at google dot com 2009-12-11 0:23 ` ramana at gcc dot gnu dot org 2009-12-11 0:25 ` ramana at gcc dot gnu dot org 2009-12-11 7:54 ` carrot at google dot com 2009-12-12 1:08 ` rearnsha at gcc dot gnu dot org 2010-03-20 13:00 ` steven at gcc dot gnu dot org 2010-04-08 9:28 ` carrot at gcc dot gnu dot org 2010-04-08 9:30 ` 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=20091015081858.2962.qmail@sourceware.org \ --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).