From: David Daney <ddaney@caviumnetworks.com>
To: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Fwd: Re: FW: gcc4.4.1 related doubt
Date: Fri, 26 Mar 2010 23:32:00 -0000 [thread overview]
Message-ID: <4BAD0C55.6070208@caviumnetworks.com> (raw)
Bah! here is the non bouncing version (I hope).
-------- Original Message --------
Subject: Re: FW: gcc4.4.1 related doubt
Date: Fri, 26 Mar 2010 11:38:20 -0700
From: David Daney <ddaney@caviumnetworks.com>
To: Ian Lance Taylor <iant@google.com>
CC: trisha yad <trisha1march@gmail.com>, Jie Zhang
<jie@codesourcery.com>, gcc-help@gnu.org, arm-gnu@codesourcery.com
On 03/26/2010 10:27 AM, Ian Lance Taylor wrote:
> trisha yad<trisha1march@gmail.com> writes:
>
>> arm-linux-gnueabi-gcc -fno-optimize-sibling-calls -O2 test.c
>> I can see Function name Convert to
>> 0000842c t T.12
>
> You still haven't explained what is wrong with that symbol. Why does
> it matter?
I thought I already said this, but here it is again:
Some broken Linux kernel build scripts flag the presence of these
symbols a something very bad. If you try building a kernel containing
these scripts, you might be lead to think that the end of the world is near.
Obviously the way to fix the problem is to change GCC so it doesn't
trigger the emission of these messages in the defective kernels. :-)
David Daney
next reply other threads:[~2010-03-26 19:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 23:32 David Daney [this message]
2010-03-26 23:35 ` Brian Budge
2010-03-26 23:37 ` David Daney
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=4BAD0C55.6070208@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=gcc-help@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).