Hi,
On 9 July 2016 at 11:27, André Przywara wrote:
> On 09/07/16 15:38, Simon Glass wrote:
>> On 8 July 2016 at 08:18, Andre Przywara wrote:
>>> As printf calls may be executed quite early, we should avoid using any
>>> BSS stored variables, since some boards put BSS in DRAM, which may not
>>> h
On 09/07/16 15:38, Simon Glass wrote:
> On 8 July 2016 at 08:18, Andre Przywara wrote:
>> As printf calls may be executed quite early, we should avoid using any
>> BSS stored variables, since some boards put BSS in DRAM, which may not
>> have been initialised yet.
>> Explicitly mark those "static
On 07/09/2016 04:38 PM, Simon Glass wrote:
On 8 July 2016 at 08:18, Andre Przywara wrote:
As printf calls may be executed quite early, we should avoid using any
BSS stored variables, since some boards put BSS in DRAM, which may not
have been initialised yet.
Explicitly mark those "static global
On 8 July 2016 at 08:18, Andre Przywara wrote:
> As printf calls may be executed quite early, we should avoid using any
> BSS stored variables, since some boards put BSS in DRAM, which may not
> have been initialised yet.
> Explicitly mark those "static global" variables as belonging to the
> .dat
As printf calls may be executed quite early, we should avoid using any
BSS stored variables, since some boards put BSS in DRAM, which may not
have been initialised yet.
Explicitly mark those "static global" variables as belonging to the
.data section, to keep tiny-printf clear of any BSS usage.
Si
5 matches
Mail list logo
