From: Ian Lance Taylor <iant@google.com>
To: trisha yad <trisha1march@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: gcc4.4.1 related doubt
Date: Thu, 25 Mar 2010 21:18:00 -0000 [thread overview]
Message-ID: <mcreij8tjds.fsf@dhcp-172-17-9-151.mtv.corp.google.com> (raw)
In-Reply-To: <cbcdf5441003250733r9cc2bd1g89dec83030b7d400@mail.gmail.com> (trisha yad's message of "Thu\, 25 Mar 2010 20\:03\:26 +0530")
trisha yad <trisha1march@gmail.com> writes:
> I am attaching one sample program.
>
> 1. arm-linux-gnueabi-gcc -fno-optimize-sibling-calls -O0 test.c
> 2. arm-linux-gnueabi-gcc -fno-optimize-sibling-calls -O2 test.c
> arm-linux-gnueabi-nm of O0 is log1
> arm-linux-gnueabi-nm of O2 is log
>
>
> I am attaching o/p of command using option --save-temps i.e in file test.s
> arm-linux-gnueabi-gcc -fno-optimize-sibling-calls --save-temps -O2 test.c
I don't understand how the .c file you showed can produce the .s file
that you showed. In the .c file, main calls ABC. In the .s file, it
does not. I don't see how the optimizer could remove that call.
I do see the T.12 symbol in the assembler source. However, I don't
know where it came from. I don't see when I compile your C file with
a recent ARM gcc.
Can you explain why the T.12 symbol is a problem?
Ian
next prev parent reply other threads:[~2010-03-25 17:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 12:41 trisha yad
2010-03-24 20:01 ` Ian Lance Taylor
2010-03-24 20:58 ` David Daney
[not found] ` <cbcdf5441003242247o42bf8854oc3ad02a77ea66589@mail.gmail.com>
[not found] ` <mcrzl1wtspc.fsf@dhcp-172-17-9-151.mtv.corp.google.com>
2010-03-25 18:55 ` trisha yad
2010-03-25 19:33 ` trisha yad
2010-03-25 21:18 ` Ian Lance Taylor [this message]
2010-03-26 14:01 ` Jie Zhang
[not found] ` <cbcdf5441003260359h70af952p62e532e98bab1cf0@mail.gmail.com>
[not found] ` <cbcdf5441003260451x184cef62q73d7be3bcaaa6136@mail.gmail.com>
2010-03-26 18:34 ` trisha yad
2010-03-26 19:35 ` Jie Zhang
2010-03-26 20:05 ` FW: " Ian Lance Taylor
[not found] ` <4BACFF1C.8010703@caviumnetworks.com>
2010-03-27 11:01 ` trisha yad
2010-03-27 9:15 ` Jie Zhang
2010-03-27 17:31 ` trisha yad
2010-03-27 19:22 ` Jie Zhang
[not found] ` <4BB0E5D0.8050803@caviumnetworks.com>
2010-04-16 13:53 ` trisha yad
2010-04-16 20:40 ` Ian Lance Taylor
[not found] <o2ucbcdf5441004150035x4ed39becsf84b311d27f43c9b@mail.gmail.com>
[not found] ` <r2hcbcdf5441004150334h38d4aaafwaa982830de73ea1f@mail.gmail.com>
[not found] ` <mcreiigpzqp.fsf@dhcp-172-17-9-151.mtv.corp.google.com>
2010-04-16 5:09 ` trisha yad
2010-04-16 5:12 ` trisha yad
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=mcreij8tjds.fsf@dhcp-172-17-9-151.mtv.corp.google.com \
--to=iant@google.com \
--cc=gcc-help@gcc.gnu.org \
--cc=trisha1march@gmail.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).