From: daniel tian <daniel.xntian@gmail.com>
To: Jeff Law <law@redhat.com>
Cc: gcc@gcc.gnu.org, peng.zheng@mavrixtech.com, yan.hu@mavrixtech.com.cn
Subject: Re: Insn missing in Size optimization(-Os)
Date: Fri, 04 Dec 2009 07:01:00 -0000 [thread overview]
Message-ID: <121fadb80912032301p6026675awc0168a8692087670@mail.gmail.com> (raw)
In-Reply-To: <4B16A54D.2020600@redhat.com>
> When a pseudo which has an equivalent form (via the REG_EQUIV note) fails to
> get a hard register, reload deletes the insn which sets the pseudo and
> instead will reload the equivalent form into a suitable hard register prior
> to use points.
>
> What you want to do is look at the reloads generated for insn #9. I'd
> hazard a guess one of them loaded the value (symbol_ref ("fun")) into R0.
> Then for some reason (you'll have to figure that out), the reload insn
> which sets R0 was deleted (or possibly doesn't get emitted because reload
> thought it was unncessary).
>
Yeah. The Move Symbol to R0 register is deleted, which is weird.
And I still can not figure out why. Which means I still need to dig it.
But I found when I used the gcc-4.0.2 version, the Call insn call the
function direction
call the function symbol which is OK.
I mean how gcc determine to call the function directly with the function symbol
or move the function symbol ref into a register then call the register.
Obviously, now the gcc-4.3.0 in my porting is working in the latter one.
Do your guys have any advice?
Thanks very much.
best regards.
daniel.tian
next prev parent reply other threads:[~2009-12-04 7:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-02 10:18 daniel tian
2009-12-02 12:29 ` daniel tian
2009-12-02 16:21 ` Ian Lance Taylor
2009-12-02 17:35 ` Jeff Law
2009-12-04 7:01 ` daniel tian [this message]
2009-12-05 8:01 ` daniel tian
2009-12-05 16:18 ` Jeff Law
2009-12-07 3:10 ` daniel tian
2009-12-08 4:04 ` Jeff Law
2009-12-08 6:11 ` daniel tian
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=121fadb80912032301p6026675awc0168a8692087670@mail.gmail.com \
--to=daniel.xntian@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=law@redhat.com \
--cc=peng.zheng@mavrixtech.com \
--cc=yan.hu@mavrixtech.com.cn \
/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).