From: Erik Christiansen
Sent: Monday, March 18, 2013 2:58 PM
> was too busy with why the existing script does not need customised
> flashN counts, to concisely answer the question directly. We can do it.
> If we move the .flashN output sections from the script template to being
> generated by individual avr6X.sh files, then the number of pages will be
> customised according to device. That still doesn't seem very useful to
> me, though, since the excess empty .flashN sections harmlessly vanish if
> not populated. Is there another reason for doing it, or do your
> avr-objdump results not show that unpopulated .flashN sections vanish?
> (With zero memory cost.)
>
If a user reads the headers or the linker scripts directly, the extra
sections could be misleading for the user.
Making it specific per architecture
ld/emulparams/<arch>.sh is made to contain the flash size or can be deduced,
the info can be used up here to control the number of sections.
Those comments were immediate thoughts that came across when I saw the scripts.
> Erik
>
> --
> What is this talk about releases? We do not make software "releases".
> Our software escapes, leaving a bloody trail of designers
> and quality assurance people in its wake! - Klingons
Like your signature. Some of the interesting uses of using Mutt I believe ;)
-George-
_______________________________________________
AVR-GCC-list mailing list
AVR-GCC-list@nongnu.org
https://lists.nongnu.org/mailman/listinfo/avr-gcc-list
