[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [avr-gcc-list] a symbol for end of program memory used?

From: Dave Hylands
Subject: Re: [avr-gcc-list] a symbol for end of program memory used?
Date: Fri, 30 Apr 2010 07:23:55 -0700

Hi Erik,

On Fri, Apr 30, 2010 at 1:34 AM, Erik Christiansen
<address@hidden> wrote:
> On Thu, Apr 29, 2010 at 07:31:55AM -0700, Dave Hylands wrote:
>> On Thu, Apr 29, 2010 at 6:18 AM, Erik Christiansen wrote:
> Incidentally, that was "23:18:32 +1000" at my keyboard. At 6:18 AM, it
> would have been well past my bedtime. Your MUA is converting to UTC?

Interesting. I'm using gmail. It seems to have converted the time to
my local time or something close to it. As I type this, it's 7:20 AM,
and gmail tells me the email showed up at 1:34 AM (5 hours ago) (the 5
hours ago bit is added by gmail). 1:34 was 5.75 hours ago, so it
appears to have converted to my local timezone.


>   __vacant_flash = DEFINED (__eeprom_in_flash) ? __data_load_end +
>                    SIZEOF(.eeprom) : __data_load_end ;
>   /* ld should't care whether it's one line or wrapped. */
> Now there will by default be no wasted flash bytes, because
> __vacant_flash = __data_load_end , but when we use on the commandline:
> ld --defsym __eeprom_in_flash=1    # Or in gcc-friendly syntax:
> avr-gcc ... -D eeprom_in_flash

Actually, I'm pretty sure this last one won't work. -D defines a
pre-processor symbol. I think you'd need to use something like

avr-gcc ... -Wl,--defsym,__eeprom_in_flash=1

> then our linker script will obediently shuffle __vacant_flash up to make
> room for .eeprom.
> Will that do?

That looks to be generic enough to be useful.

Dave Hylands
Shuswap, BC, Canada

reply via email to

[Prev in Thread] Current Thread [Next in Thread]