public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dferbas at etech dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/41302]  New: Cast of return value from uint32 to pointer cannot be optimized by a jump to called rtn.
Date: Mon, 07 Sep 2009 22:24:00 -0000	[thread overview]
Message-ID: <bug-41302-18166@http.gcc.gnu.org/bugzilla/> (raw)

Called fn returns value in d0 (non pointer), but findZipEntry should return
value in a0 (address register). So in that case optimization cannot be done by
simply jumping to the called fn.

typedef u_int32_t       w_word;
typedef struct *        z_zipEntry;

z_zipEntry findZipEntry(z_zipFile dir, w_byte *name) {

        return (z_zipEntry) ht_read(dir->ht, (w_word)name);
}


findZipEntry:
        move.l 4(%sp),%a0
        move.l 8(%a0),4(%sp)

        jra ht_read

There should be:
        jbsr ht_read
        move.l %d0,%a0
        rts


-- 
           Summary: Cast of return value from uint32 to pointer cannot be
                    optimized by a jump to called rtn.
           Product: gcc
           Version: 4.3.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: dferbas at etech dot cz


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


             reply	other threads:[~2009-09-07 22:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-07 22:24 dferbas at etech dot cz [this message]
2009-09-09 22:14 ` [Bug target/41302] " rth at gcc dot gnu dot org
2009-09-22 22:39 ` dferbas at etech dot cz
2009-10-30 10:16 ` mkuvyrkov at gcc dot gnu dot org
2009-11-04  9:58 ` mkuvyrkov at gcc dot gnu dot org
2009-11-04 11:47 ` mkuvyrkov 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=bug-41302-18166@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).