[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lwip-devel] [bug #35587] Uninitialized pointer
From: |
Eliot Blennerhassett |
Subject: |
Re: [lwip-devel] [bug #35587] Uninitialized pointer |
Date: |
Fri, 24 Feb 2012 12:25:39 +1300 |
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111108 Thunderbird/3.1.16 |
> From: Mason <address@hidden>
>
> David Brown wrote:
>
>> TI's Code
>> Composer is one of these - it does not zero the statically allocated
>> uninitialised data at startup (unless you add your own code to do so).
>> It even has a comment in the manual, telling you that this behaviour is
>> non-standard!
>
> It is worse than non-standard, it is non-conforming.
>
> In other words, such a compiler is NOT a C compiler,
> whatever the manufacturer claims in the documentation
> or elsewhere.
Actually it is perfectly valid for the C *compiler* to behave like this.
The problem is with the default settings of the overall toolchain,
specifically the C initialization code, the linker or the program loader.
--
Eliot
- Re: [lwip-devel] [bug #35587] Uninitialized pointer,
Eliot Blennerhassett <=