search

BigEd / atalan

Automatically exported from code.google.com/p/atalan
MIT License
1 stars 0 forks source link

Temporary variables on page 0 go out #13

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
When there is many calculations, many temporary variables are placed on page0, 
but there is no checking. In result this collides with stack.

Original issue reported on code.google.com by jakub.hu...@gmail.com on 30 Aug 2010 at 9:18

GoogleCodeExporter commented 9 years ago 
It would be fine to alloc some place somewhere in the memory, for example after 
 or before code, or stricte given address. I have realised that it is not 
critical to store them on ZP (switch in compiler)

Original comment by jakub.hu...@gmail.com on 31 Aug 2010 at 6:30

GoogleCodeExporter commented 9 years ago 
By "switch in compiler" I mean to add the switch that would set the variable 
memory to some place, automatic, or ZP.

Automatic would choose:
- the most used variables to fit on ZP (optimize for size)
- the deepest used variables to fit on ZP (optimize for speed)

Original comment by jakub.hu...@gmail.com on 3 Sep 2010 at 12:53

GoogleCodeExporter commented 9 years ago 
Variable memory may be defined in platform definition even out of ZP.
Implemented variable reuse algorithm that eliminates many temporary variables.

Original comment by rudla.ku...@gmail.com on 1 Nov 2012 at 5:47

GoogleCodeExporter commented 9 years ago

Original comment by rudla.ku...@gmail.com on 1 Nov 2012 at 5:47