public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/17959] New: -mpowerpc64 can cause worse code than without it Date: Tue, 12 Oct 2004 23:01:00 -0000 [thread overview] Message-ID: <20041012230130.17959.pinskia@gcc.gnu.org> (raw) unsigned long long div16(unsigned long long n) { return n / 16; } Without -mpowerpc64: _div16: slwi r0,r3,28 srwi r4,r4,4 or r4,r0,r4 srwi r3,r3,4 blr With: _div16: li r0,0 rldimi r0,r3,32,0 rldimi r0,r4,0,32 srdi r4,r0,4 srdi r3,r0,36 blr -- Summary: -mpowerpc64 can cause worse code than without it Product: gcc Version: 4.0.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: enhancement Priority: P2 Component: target AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: pinskia at gcc dot gnu dot org CC: gcc-bugs at gcc dot gnu dot org GCC target triplet: powerpc-darwin http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17959
next reply other threads:[~2004-10-12 23:01 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-10-12 23:01 pinskia at gcc dot gnu dot org [this message] 2004-10-12 23:03 ` [Bug target/17959] " pinskia at gcc dot gnu dot org 2004-11-28 8:27 ` amodra at bigpond dot net dot au
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=20041012230130.17959.pinskia@gcc.gnu.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).