public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sliao at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/42499] Bad register allocation in multiplication code by constant
Date: Thu, 07 Jan 2010 12:44:00 -0000	[thread overview]
Message-ID: <20100107124357.14712.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42499-17572@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from sliao at google dot com  2010-01-07 12:43 -------
Because:
"This bug can be more easily demonstrated with multiplication of tv_sec by 10
and tv_usec/ 1000 removed"

, the input program is:
#include <sys/time.h>

extern void get_time(struct timeval*);

void test(long long *res)
{
    struct timeval tv;
    get_time(&tv);
    *res = tv.tv_sec * 10;
}

As a result, there is no load of tv.tv_usec in the code generated. Sorry for
the confusion.


-- 

sliao at google dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jingyu at google dot com,
                   |                            |dougkwan at google dot com,
                   |                            |carrot at google dot com


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


  parent reply	other threads:[~2010-01-07 12:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-25 10:12 [Bug rtl-optimization/42499] New: " sliao at google dot com
2009-12-31 15:30 ` [Bug rtl-optimization/42499] " rguenth at gcc dot gnu dot org
2010-01-05 18:28 ` ramana at gcc dot gnu dot org
2010-01-07 12:44 ` sliao at google dot com [this message]
2010-01-07 12:55 ` sliao 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=20100107124357.14712.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).