public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dje at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/17103] Opportunity to replace multiply with shift/add sequence Date: Sun, 12 Sep 2004 20:37:00 -0000 [thread overview] Message-ID: <20040912203757.25080.qmail@sourceware.org> (raw) In-Reply-To: <20040819145911.17103.steinmtz@us.ibm.com> ------- Additional Comments From dje at gcc dot gnu dot org 2004-09-12 20:37 ------- On POWER4, the default processor, the latency of mulli relative to shifts and adds makes mulli a better choice than synthesizing the multiply by constant. When tuning for other PowerPC processors, such as POWER3, the synthesized sequence is generated. -- What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17103
prev parent reply other threads:[~2004-09-12 20:37 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-08-19 14:59 [Bug other/17103] New: " gcc-bugzilla at gcc dot gnu dot org 2004-08-19 15:34 ` [Bug middle-end/17103] " pinskia at gcc dot gnu dot org 2004-08-19 15:46 ` [Bug target/17103] " falk at debian dot org 2004-09-12 20:37 ` dje at gcc dot gnu dot org [this message]
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=20040912203757.25080.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).