From: David Daney <ddaney@caviumnetworks.com>
To: Brian Budge <brian.budge@gmail.com>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: FW: gcc4.4.1 related doubt
Date: Fri, 26 Mar 2010 23:37:00 -0000 [thread overview]
Message-ID: <4BAD19C5.7050205@caviumnetworks.com> (raw)
In-Reply-To: <5b7094581003261305l7cb866dfr9442005df40b8648@mail.gmail.com>
On 03/26/2010 01:05 PM, Brian Budge wrote:
> Doesn't it seem like fixing the broken scripts might be better?
Probably you are right.
> And if not, why not?
>
No good reason that I can think of.
I would note, that the current Linux kernel HEAD does not suffer this
problem. There was however a window between when the bogus warning
messages were added to the kernel build scripts and the release of a GCC
version that triggered the issue. Once the kernel hackers realized
there was a problem, they fixed it. People using the kernel versions in
the window either have to use older GCCs or fix their build scripts if
they don't want to see the messages.
Fixing the kernel build scripts is not difficult, but I forgot what I
did, so it is left as an exercise for the enterprising reader.
David Daney
> On Fri, Mar 26, 2010 at 12:34 PM, David Daney<ddaney@caviumnetworks.com> wrote:
>> 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 prev parent reply other threads:[~2010-03-26 20:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 23:32 Fwd: " David Daney
2010-03-26 23:35 ` Brian Budge
2010-03-26 23:37 ` David Daney [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-03-24 12:41 trisha yad
2010-03-24 20:01 ` Ian Lance Taylor
[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 21:18 ` Ian Lance Taylor
2010-03-26 14:01 ` Jie Zhang
[not found] ` <cbcdf5441003260359h70af952p62e532e98bab1cf0@mail.gmail.com>
[not found] ` <cbcdf5441003260451x184cef62q73d7be3bcaaa6136@mail.gmail.com>
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
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=4BAD19C5.7050205@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=brian.budge@gmail.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).