public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cosmos at claycon dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/55393] gcc/g++ multiplies two unsigned integers using the IMULQ instruction
Date: Tue, 20 Nov 2012 07:46:00 -0000	[thread overview]
Message-ID: <bug-55393-4-pMQQTuEqcw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55393-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #2 from Clay Harris <cosmos at claycon dot org> 2012-11-20 07:46:15 UTC ---
I shouldn't write bug reports when I've been awake for 24 hours.

The bit 63 reference was for one more 9 in num, which got missed
with a cut & paste error.  In any case, the IMUL instruction is doing
what its supposed to for the C code (and executes faster than MUL).
The handling of the sign bit would be wrong, except that we're
throwing away the upper half of the product, where the discrepancy
would occur.

It would be very convenient for overflow testing to have the upper
half (or at least the Carry flag), but alas gcc doesn't seem to have
a way to do that since long long int stopped being 128 bits in 64bit
mode.

Please close this bug as INVALID.


  parent reply	other threads:[~2012-11-20  7:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-19 11:28 [Bug c++/55393] New: " cosmos at claycon dot org
2012-11-19 14:03 ` [Bug rtl-optimization/55393] " jakub at gcc dot gnu.org
2012-11-20  7:46 ` cosmos at claycon dot org [this message]
2012-11-20  7:56 ` jakub 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=bug-55393-4-pMQQTuEqcw@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: 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).