From: Andrew Haley <aph@redhat.com>
To: sumanth <sumanth.gundapneni@redpinesignals.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Passing arguments of function through registers
Date: Tue, 10 Feb 2009 11:54:00 -0000 [thread overview]
Message-ID: <4991681B.7030501@redhat.com> (raw)
In-Reply-To: <499165AF.6090503@redpinesignals.com>
sumanth wrote:
> I am running with -Os level optimization level.
> For the time being assume the processor is arm processor .
OK. Current gcc (4.4 pre) does this with -Os:
00000000 <add>:
0: e0811000 add r1, r1, r0
4: e0810002 add r0, r1, r2
8: e12fff1e bx lr
> Guess I can resolve this with gcc-3.3 itself.
Maybe. I'm quite surprised that any version of gcc generated code
as bad as what you posted.
Andrew.
prev parent reply other threads:[~2009-02-10 11:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 11:21 sumanth
2009-02-10 11:28 ` Andrew Haley
[not found] ` <499165AF.6090503@redpinesignals.com>
2009-02-10 11:54 ` Andrew Haley [this message]
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=4991681B.7030501@redhat.com \
--to=aph@redhat.com \
--cc=gcc-help@gcc.gnu.org \
--cc=sumanth.gundapneni@redpinesignals.com \
/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).