> By default all the constant variables will be stored in the far memory
> ('.frodata' section) and will be accessed using "LDE" instruction. The
> non-initialized non-constant variables will be stored in near memory
> ('.nbss' section) and will be accessed using "MOV" instructions. The
> initiali
Hi DJ,
>> From the above, I think I like this plan:
Please ignore my earlier post on this topic. We have modified the
proposed solution to incorporate your suggestions. We would be glad if
you could verify it again.
By default all the constant variables will be stored in the far memory
('.frodat
Hi DJ,
By default all the constant variables will be stored in the far memory
('.frodata' section) and will be accessed using "LDE" instruction. The
non-initialized non-constant variables will be stored in near memory
('.nbss' section) and will be accessed using "MOV" instructions. The
initialize
> - 2 new attributes "far_data" (to use external memory for data
> storage) and "far_rodata" will be added.
I'd prefer just one "far" attribute. GCC knows (usually better than
the user ;) what data is read-only and what data is not.
> - By default, LDE instructions will be used to access the en
Hi,
We have come up with two possible solutions to solve the 20 bit data
access problem in m16c targets.
We are very grateful for all the suggestions until now on this issue.
Solution 1 is based on the discussion at the following link -:
http://gcc.gnu.org/ml/gcc/2007-04/msg00402.html
- 2 new at
