English Amiga Board - View Single Post

VladR · 20 March 2024, 16:13

While working on my RTG benchmark, I want to dedicate one of the tests to differences between ChipRam and FastRam.

I'm using vasm and hunkexe format, so it should be a relocatable format (no .ORG or absolute memory addresses anywhere).

When I printed the addresses of the first/last line of code and data at run-time, I noticed that they are all in FastRAM (unless I change the attribute in the SECTION to use chipram) - well based on the range that SysInfo gives me under WinUAE.

Is that guaranteed, though ? I am not using AllocMem and all my data is compile-time allocated (for now). It would be of great benefit if I didn't have to refactor the code to use AllocMem and both code/data would be guaranteed to be placed in FastRAM.

I do not intend to run it below 040 initially, and some time in the future, I might try to make it run on slowest RTG config (A1200, I suspect) - but for now, let's say 040.

20 March 2024, 16:13	#1
VladR Registered User Join Date: Dec 2019 Location: North Dakota Posts: 741	Placement of code and data in FastRam While working on my RTG benchmark, I want to dedicate one of the tests to differences between ChipRam and FastRam. I'm using vasm and hunkexe format, so it should be a relocatable format (no .ORG or absolute memory addresses anywhere). When I printed the addresses of the first/last line of code and data at run-time, I noticed that they are all in FastRAM (unless I change the attribute in the SECTION to use chipram) - well based on the range that SysInfo gives me under WinUAE. Is that guaranteed, though ? I am not using AllocMem and all my data is compile-time allocated (for now). It would be of great benefit if I didn't have to refactor the code to use AllocMem and both code/data would be guaranteed to be placed in FastRAM. I do not intend to run it below 040 initially, and some time in the future, I might try to make it run on slowest RTG config (A1200, I suspect) - but for now, let's say 040.