Paul Schlie wrote:
More specifically, there seem to be two predominant motivating reasons why it may be desired to attach a target specified attributes to compiler generated static constant objects:
1 - To enable their identification so that their compile/link time storage location/type may be influenced by the target.
2 - To enable their identification so that their run-time access method may be influenced by the target. (Likely due to their storage location/type)
I know that you are doing this for the AVR target.
You are under the assumption that it is acceptable to attach attributes to static constant objects to put data in Program Space for the AVR target.
As Joseph pointed out to you in bug #20258, <http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20258> implementing DTR 18037 is the best way to go about this.
You consistently do not check with the official AVR maintainers (Denis Chertykov and Marek Michalkiewicz), or on the avr-gcc-list <http://savannah.nongnu.org/mail/?group=avr> to see if any of this will fly with the rest of the AVR community.
Eric
