|
From: | David Brown |
Subject: | Re: [avr-gcc-list] Allocation sequence of eeprom variables |
Date: | Mon, 20 Aug 2012 22:10:30 +0200 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111108 Fedora/3.1.16-1.fc14 Lightning/1.0b3pre Thunderbird/3.1.16 |
On 20/08/12 16:18, Juergen Harms wrote:
I am presently switching from a rather obsolete version of avr-gcc (1.6.1, downloaded as a tarball) to a much newer one (4.6.2, available in an rpm package on my Mageia distribution), I am having a lot of small-fry but work-intensive problems (risk of editing new bugs into my code) - such as the need to declare progmem variables with "const"- and some annoyance with "-Wuninitialized" warning messages when declaring external variables wich have been perfectly correctly defined and initialised in their target module.
Almost certainly, there is something wrong in your code, or in the way you have declared your external data - the "-Wuninitialized" flag should not give false positives as you describe. (It can give false positives, when you know yourself that all code paths that use the data have initialised the variables but the compiler is unable to prove this.)
[Prev in Thread] | Current Thread | [Next in Thread] |