![]() |
@olaf
"The value of the Amiga assets does not grow, because the owners do not invest enough time and energy to get the measure of, maintain or improve its value." I think you may be spot-on there sir. |
Quote:
- LEA/PEA are always absolute, even if EA is inside +-32kb and it is in same module. - Always JSR 12345678, never BSR (same as above) - cmp.w #0,An; Bcc vs (if unused data register is available) move.l/w An,unused Dn; Bcc - move.l 4.l,A6, never move.l 4.w,a6 Fixing these would save lots of bytes and also increase performance a bit. |
Quote:
For the game I am working on, I am using bebbo's gcc, but with my hacks to enable me to use vasm/vlink. vasm does some of what you describe above for me, and if I compare the code size of the main game code (no data) between no vasm optimisations and the (potentially unsafe, but seems to work fine) vasm optimisations I use, this is the size difference: potentially unsafe optimisations: 48600 bytes no optimisations: 51092 bytes Speed wise, this number is the number of scan lines taken to render a game recording: potentially unsafe optimisations: 653275 no optimisations: 657640 So not a bad size gain and a tiny speed increase. For the record, these are the vasm optimisations I use: -Wa,-opt-allbra -Wa,-opt-brajmp -Wa,-opt-lsl -Wa,-opt-movem -Wa,-opt-mul -Wa,-opt-div -Wa,-opt-pea |
Quote:
|
Quote:
|
Quote:
http://eab.abime.net/showthread.php?t=85474 Quote:
Quote:
Quote:
Quote:
Quote:
|
Quote:
(And yes, Space Ace was the name of the other one. But I can't find that bug when looking for it now. How certain I was...) |
Quote:
|
Quote:
|
Quote:
|
Quote:
The pattern should be $41f8,$1000,$43fa. The $1000 is the start address, but changing it to $8000 and above is $ffffxxxx equivalent IIRC. Replace $1000 with $7000 and recalculate the ROM checksum. |
@NorthWay
I ask this because one of the issues with exec 45.20 on the MacroSystem DraCo is that it has no memory at all at zero address, unless the AmigaOS MMU setup is still active,and then it's only virtual. DraCo memory starts at 0x4000 0000, 0x4200 0000, 0x4400 0000, 0x4600 0000, with at least 4 MB in the first slot, and not more than 32 MB in each slot. The AmigaOS MMU table is somewhere in the first 2 MB. A full 128 MB DraCo looks like this with NetBSD: memory segment 0 at 40000000 size 00200000 memory segment 1 at 40200000 size 07e00000 So patching exec 45.20 to acomodate that might have a chance to make it viable on this machine, because currently, it just doesnt work. |
Quote:
Quote:
Quote:
Compared to other "platforms", that have open source communities - the AmigaOS community is very uncooperative/hostile unless you just agree and nod to everything, and this is a comment that's often made sadly. IMHO this is partly because the small community that remains have been manipulated by the few people who can milk them, into keeping things that way. |
Quote:
|
Quote:
|
@Kalamatee
All very well-observed points there sir. I might add that the bad seed of hostility was probably borne of Commodore's demise, and all of the terrible consequences that came of that. To be an Amiga user was somehow linked with strange psychological abuse early on. |
@Kalamatee
All very well-observed points there sir. I might add that the bad seed of hostility was probably borne of Commodore's demise, and all of the terrible consequences that came of that. To be an Amiga user was somehow linked with strange psychological abuse early on. |
Quote:
If and when somebody figures out who is actually responsible for making decisions on the fate of the Amiga operating system, and in addition being responsible for it, is also able to make changes stick, we'll know for sure what immediate obstacles exist. Until then there is just speculation. |
olaf, if you dont know for sure, who of us is supposed to know? ;)
|
Quote:
Seriously, this is in my opinion a side-effect of very few players remaining in this field who can to a certain degree control what products may be made and sold. How much control they actually have is limited by budget constraints, personnel involved, time available, actual sales and legal restrictions. Few players being involved means that any decision made by them can instantly have far reaching effects on the market, the business and the hobbyists, both for better and for worse. The limitations which the players have to work under always dictate how much risk they may be able to take, also for better and worse. Finally, there is also competition between the players, among and against each other, which adds another level of risk and uncertainty on top. If this were any other kind of business, would you reasonably want to be involved in it? You mentioned milking. I believe that the term may not apply here. The constraints are not created by the players, they just have very little room to conduct their businesses. This in turn leads to the sometimes baffling decisions as to what kind of product can be released, and at which price. |
All times are GMT +2. The time now is 01:31. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.