18 August 2018, 12:32 | #1 |
Semi-Retired
Join Date: Mar 2012
Location: Leiden / The Netherlands
Posts: 2,055
|
Preventing hunk merger with vlink
Hi,
It is possible to tell vlink not to merge bss and/or data hunks? I want to do the following: compile multiple 68k sources to one 68k object file, then compile multiple ppc sources to one ppc object file. Both with merging enabled. Then I'd like to link the two to a WarpOS executable, but want the data hunks of the 68k not merged with the ppc data hunks (as happens now). I'm specifically looking at the Quake source on Frank Wille's site (which is down atm). It is to test if interrupt code and/or data placed in PCI memory (with a PCI PPC card and Mediator) is to blame for sound not working on A1200 mediators with a PCI PPC card. I want to push this 68k data/code forcibly to Fast RAM (after compiling setting bit 31 of the 68k data and code hunks). As said, as a test. Thanks for any help. |
18 August 2018, 15:18 | #2 | ||||
Natteravn
Join Date: Nov 2009
Location: Herford / Germany
Posts: 2,552
|
As with most linkers, just give the sections different names.
Do not specify -sd (small data), which will merge all data and bss. Quote:
Quote:
Quote:
Quote:
For the data I would use a trick: Just make sure all relevant data for your sound interrupt routine is in a structure, which can be referenced via a pointer. So only the pointer will be placed into .tocd. The structure will be in .data or .bss, which is a separate section. I'm certainly lacking some information here. Maybe a map file from vlink (-M option) shows some more details about your linking process. |
||||
24 August 2018, 14:40 | #3 |
Semi-Retired
Join Date: Mar 2012
Location: Leiden / The Netherlands
Posts: 2,055
|
Thanks for your reply. The part about the toc makes sense. Bummer.
And yes, ppc code and 68k code ends up in different hunks but as they are all $3e9 I cannot differentiate between them easily using detection code. Anyway, I did it all manually (moving 68k code hunks to the correct ram) but it still crashes on the 1200. Maybe I should try to understand more how AHI hooks work....Cause i think the problem lies in there somewhere. |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Preventing background interaction when running in QAMIGA mode | earok | Coders. Blitz Basic | 4 | 05 April 2018 02:06 |
WinUAE preventing screensaver | trumpy81 | support.WinUAE | 7 | 13 March 2018 00:35 |
Trying out vlink and vasm | cla | Coders. General | 2 | 30 September 2016 20:30 |
CIA & VITNO Retrogaming Forum upgraded to vB 4.2.1 & Merger | DH | News | 1 | 19 September 2016 21:39 |
Preventing amigas from getting yellow with time | paulo_becas | support.Hardware | 19 | 28 June 2015 16:17 |
|
|