public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dann at godzilla dot ics dot uci dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/16532] Inefficient jump to epilogue
Date: Thu, 19 Aug 2004 16:58:00 -0000	[thread overview]
Message-ID: <20040819165806.28355.qmail@sourceware.org> (raw)
In-Reply-To: <20040713215437.16532.dann@godzilla.ics.uci.edu>


------- Additional Comments From dann at godzilla dot ics dot uci dot edu  2004-08-19 16:58 -------
(In reply to comment #6)

> However, this optimization is partially defeated by the 32-bit calling
> convention in the testcase, so I'm not sure it is really worth while there.

I forgot to say that Sun's compiler does not generate a "save"

BTW, any idea why the generated v8 code: 

        srl     %o0, 16, %o5
        mov     0, %o4
        orcc    %o4, %o5, %g0
        [snip]

is not simplified to:

        srl     %o0, 16, %o5
        orcc    %o5, 0, %g0

Also the v9 code does not seem to realize that it can do a 16 bit shift of a 
32bit register instead of a 48bit shift of a 64bit register. This might help if
the register pressure is high (which is not the case here).




-- 


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


  parent reply	other threads:[~2004-08-19 16:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-13 21:54 [Bug rtl-optimization/16532] New: duplicate function epilogue on sparc dann at godzilla dot ics dot uci dot edu
2004-07-13 22:31 ` [Bug target/16532] " pinskia at gcc dot gnu dot org
2004-07-14  7:29 ` [Bug target/16532] Inefficient jump to epilogue ebotcazou at gcc dot gnu dot org
2004-07-14  7:43 ` ebotcazou at gcc dot gnu dot org
2004-07-14 16:19 ` dann at godzilla dot ics dot uci dot edu
2004-08-18 18:30 ` dann at godzilla dot ics dot uci dot edu
2004-08-19 10:13 ` ebotcazou at gcc dot gnu dot org
2004-08-19 16:58 ` dann at godzilla dot ics dot uci dot edu [this message]
2004-09-27 20:35 ` pinskia at gcc dot gnu dot org
2004-09-28  6:26 ` cvs-commit at gcc dot gnu dot org
2004-09-28  6:34 ` ebotcazou at gcc dot gnu dot org
2004-09-28  6:57 ` ebotcazou at gcc dot gnu dot org
2004-09-28  7:00 ` ebotcazou at gcc dot gnu dot org
2004-09-28  7:14 ` ebotcazou at gcc dot gnu dot org
2004-09-28  7:17 ` ebotcazou at gcc dot gnu dot org
2004-09-28  7:18 ` ebotcazou at gcc dot gnu dot 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=20040819165806.28355.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).