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 middle-end/17958] expand_divmod fails to optimize division of 64-bit quantity by small constant when BITS_PER_WORD is 32
Date: Tue, 12 Oct 2004 22:55:00 -0000	[thread overview]
Message-ID: <20041012225537.23223.qmail@sourceware.org> (raw)
In-Reply-To: <20041012224816.17958.zack@gcc.gnu.org>


------- Additional Comments From pinskia at gcc dot gnu dot org  2004-10-12 22:55 -------
not all constants though (power of 2 are fine) for an example 16:
        mr r12,r3
        srawi r11,r3,31
        srawi r9,r11,31
        srawi r10,r11,31
        srwi r10,r9,28
        li r9,0
        addc r12,r10,r4
        adde r11,r9,r3
        srwi r4,r12,4
        insrwi r4,r11,4,0
        srawi r3,r11,4


Confirmed.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
          Component|rtl-optimization            |middle-end
     Ever Confirmed|                            |1
   Last reconfirmed|0000-00-00 00:00:00         |2004-10-12 22:55:35
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17958


  reply	other threads:[~2004-10-12 22:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-12 22:48 [Bug rtl-optimization/17958] New: " zack at gcc dot gnu dot org
2004-10-12 22:55 ` pinskia at gcc dot gnu dot org [this message]
     [not found] <bug-17958-4@http.gcc.gnu.org/bugzilla/>
2012-06-12 20:52 ` [Bug middle-end/17958] " pinskia at gcc dot gnu.org
2021-05-04 12:32 ` rguenth at gcc dot gnu.org
2021-08-15 12:14 ` pinskia at gcc dot gnu.org

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=20041012225537.23223.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: link
Be 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).