[Bug target/20288] AVR assignment of a value through a 16 bit pointer generates out of order code

[schlie at comcast dot net]

------- Additional Comments From schlie at comcast dot net  2005-03-04 14:13 -------
(In reply to comment #10)
Upon further thought, and agreeing that the explicit use of an asm macro is likely
the most appropriate near term solution; it would appear the most ideal longer
term solution would be to figure out how to comprehensively enable both explictly
and implicitly declared objects optionally tagged with target specific attributes to
influence the selection of the access method (generated code) used to access them.

Thereby allocated objects may be identified as potentially being allocated to either
ROM(progmem), EEPROM, RAM(by defalut), or even requiring a particular access
sequence (which in theory may even include the automatic wraping of interrupt
disable/enable around the access automatically).

(but it appears that a few things wihtin GCC may need to be refined to broadly
 enable the use of attributes to accomplish this, which I'm attempting to document).


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20288