7/6/2023 0 Comments Ibrowse amiga.org fpu![]() It's best to avoid extended precision immediates (trapped on 68060) and extended precision format for loading/saving except for FMOVEM.X to load/save registers. It's usually not a problem unless assumptions are made about the least significant bits in a floating point register which isn't a good idea anyway. The extended precision bits beyond a double (and some rounding bits) are left off in the register while extended precision format is supported for immediates and an. Almost no other modern mainstream CPU supports more than double float for speed. The 68k FPU was an improvement of the x86 FPU which also used a higher precision than double float extended format. Most 68k FPU "emulations" and probably even new 68k fpga/ASIC FPU's will use a 64 bit double (.D) float instead of the 80 bit FPU register/96 bit load and save extended (.X) format. ![]() Don't expect any of them to become anything more, especially not for classic Amigas. Use the current IBrowse/Voyager/Aweb for what you can, if you want to. My sentiments about the classic hardware on which they will run on remains: It can never be enough for modern standars. They would both be stuck in past standards and never become really useful for much more than browsing Aminet and other Amiga-specific sites that is specially made for "smooth-talking" these kind of incapable browsers. That is: Nowhere close to where Odyssey (for instance) is. ![]() However, I think it's pretty safe to claim that neither of these would ever come very far (if anywhere at all) from where it is today. ![]() As Itix said, it's not at all unstable, I used Voyager back on MorphOS 1.4, and its stability is definitely on par with IBrowse.Ī community bounty ("NOOO, NOT AGAIN!!!!") might be an option, but IMHO, chances are very big that both IP holders will either:Ģ) Greatly overestimate the real life value of the code today (like Magellan2 for example) You want web browsing to "continue"(?!) on classic Amigas, then:ġ) Check out the possibilities to purchase the sources of IBrowse.Ģ) Check out the possibilities to purchase the sources of Voyager. As I have said before, I can't personally see any moral obstacles for using them, as things are now. And *that* is "the programs key-files for IBrowse is obviously out in the wild. Which is kind of ironic, isn't it? It's being PPC without being "aware" of it (or indeed needing to care about it). The code actually doing the probing, will (at the moment it is being executed by the PPC CPU) be all PPC code.But maybe it's a matter of semantics as you said.? ) And it's not like that on MorphOS, where all resources are shared, the sheduler is the same, etc. There is no 68k CPU available in a MorphOS system, not even "virtual" (I don't share Itix definition there at all, my view of emulated/"virtual CPU" is in post #230, and had it been a "virtual 68k CPU" in the system in addition to the physical PPC CPU, it would mean that in the manner/context Amiga 68k apps is being executed on MorphOS, we would have a de-facto mutli-CPU system (which isn't really possible in an Amiga context, unless done in a PowerUP or AMP kind of way).If a 68k Amiga program would ask which "68k CPU" it's running on, I'm sure it would be presented as 68060 (although in practice there is a mixture of numerous instruction sets), just like Itix said. Programs (or "opcode streams" if you prefer) are de-facto rewritten, either dynamically while running, or before being started, through JIT.
0 Comments
Leave a Reply. |