Hi

Looks like Aros will win the race to 64Bit OS. How long before the others catch up.

http://www.osnews.com/story/29684/AROS_adding_64bit_and_SMP_support

_________________
A1200 ACA1232 128MB Indivison MkIICr
Elbox empty Power Tower
RPi3 Emulating C64 ZX Atari PS BBC
Wii with Amiga emulation
Vampire v4 SA

@g01df1sh

Quote:

Looks like Aros will win the race to 64Bit OS

We have 64bit for years already (Here some old news from 2007) ;-D

Last edited by michalsc on 27-Feb-2017 at 10:31 AM.

@michalsc

Yes and No

it needed some love I guess :)

@OlafS25

Quote:

it needed some love I guess :)

Indeed, the first years were like "Oh, cool." and nothing more :) Luckily it'S gaining attention now.

@OlafS25

64 bit were there since i remember it. only that most people talking aros are still about x86/abiv0 distros. its multicore support that is news. i dont know if it can exactly be called smp at this time, for the time being the system and the legacy appsapps is still supposed to be bound to the first core, for what i know.

@wawa

someone told me some time ago that 64bit Aros supports more than 100 GByte RAM already... modern hardware often has more than 4 GByte RAM already. So it is nice to have it. Of course SMP will more directly affect users than to be able to address more than 4 GByte but both combined are good to have. Finally that was what people always aksed for... 64bit, SMP and MP. Only MP then is missing

@michalsc

Quote:

Indeed, the first years were like "Oh, cool." and nothing more :) Luckily it'S gaining attention now.

it simply isnt usually a necessity for most people. like it or not but aros is a toy os, same as any other amiga flavour. you can try to use it for daily work, but eventually this or that task will force you to fire windows, mac or linux up, due to lack of professional software or attractive contemporary games. the available bunch of applications, be it os4. morphos or aros dont usually require more than 4gig of ram or multicore. so the implementation of these features is rather a question of ambition and technical curiosity. it may boost some further developments but i fear, the scene is far too limited to maintain necessary dynamics, as it is.

@OlafS25

Quote:

someone told me some time ago that 64bit Aros supports more than 100 GByte RAM already... modern hardware often has more than 4 GByte RAM already.

128GB in single Memory header IIRC (can check later if you want to know), nothing forbids having more memory headers if necessary. I test the SMP WiP code on (virtual) machine with 4,5 or 8GB ram (depending on where I work - laptop or desktop).

@OlafS25

Quote:

100 GByte RAM already...

tim.. ;)

Quote:

Only MP then is missing

one could argue there are protected zones as far as its possible. i dont think aros developers are going to introduce individual memory space for application or resign on passing messages via pointers. thats at least what has benn declared in the past. there might be some unconventional ideas floating around, but i wouldnt throw the stick too far ahead.

@michalsc

the 128 GB are nice for marketing :)

in reality you have 4 GB or 8 GB RAM, if that is supported it is enough already

128 GB would be only needed if you would use Aros as a database server or similar, not propable at the moment I guess

@michalsc

just a naive idea regarding memory protection from a user point of view

I know that it is almost impossible to introduce full memory protection without breaking everything. How about a compromise, to have full memory protection for adapted software and the existing system for old applications. The user could decide, when he uses old software he would be responsible himself if system is not 100% stable

what do you think? Possible?

@OlafS25

8GB should be enou.... Speak for yourself. My AROS machine has 32 GB. :)

_________________
Support AROS sponsor a developer.

"AROS is prolly illegal ~ Evert Carton" intentionally quoted out of context for dramatic effect

@terminills

you can use 64 GB or whatever

I am happy with 8 GB

How much RAM is available to legacy apps ? I guess apps need to be updated/recompiled to use more than 3Gb ram ?

_________________
http://www.warpdesign.fr/

@Leo

you mean 68k apps?

they run in UAE on any aros platform (except 68k of course). 68k is 32bit wherever it runs.

any application must be recompiled for the target platform, f.e. X86 Aros software not runs in X64 or ARM.

Last edited by OlafS25 on 27-Feb-2017 at 12:17 PM.

@Leo

Quote:

How much RAM is available to legacy apps ?

Ahem... Full amount.

Quote:

I guess apps need to be updated/recompiled to use more than 3Gb ram ?

Apps on 64-bit AROS are 64-bit per definition, so any of them can use as much memory as available.

@michalsc

he means if X86 apps run on X64 propably

@OlafS25

Quote:

he means if X86 apps run on X64 propably

i dont think this is how this works or is envisioned. aros has distinct separate platforms for separate architectures. windows or linux may provide x86 environemts on x64 systems to run legacy software transparently. such a necessity doesnt exist on aros (or other amiga ng platform for that matter). there is no notable pool of software that isnt open source and could not be natively recompiled for another target platform.

Last edited by wawa on 27-Feb-2017 at 12:48 PM.

@michalsc

Quote:

We have 64bit for years already (Here some old news from 2007) ;-D

Yes, I knew. But placing "64bits" and "SMP" together would have raised the "ooooh!-effect". And it did, according to comments :D

@Leo

Quote:

Leo wrote: How much RAM is available to legacy apps ? I guess apps need to be updated/recompiled to use more than 3Gb ram ?

Legacy apps are the 68K ones, already compiled to run on AmigaOS 3 and AROS68K, I guess. Is it right?

Well, since they are binary executables targeted to the Motorola 68K series of processors, the will never run on any other architecture (being it 16, 32 or 64 bit, ARM, x86, PPC, x64 or whatsoever) BEFORE being recompiled from their sources.

Once you recompile them for x64, they will become 64 bit applications and, if they can work (if there aren't mistake or assumptions preventing them to run correctly in a 64 bit address space), they will get all the memory available if they need it.