Re: [hatari-devel] Hatari on constrained devices |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] Hatari on constrained devices
- From: Thomas Huth <th.huth@xxxxxxxxx>
- Date: Fri, 7 Jan 2022 21:05:10 +0000
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1641589513; bh=jxRVq79AK/4XXDpmCm98/vnW/df90um+54wy1TecX2c=; h=Date:From:To:Subject:From; b=N5j+S9VcF1RqyidpSP4MRHUmSUrpBiUmvYacf6+2XgOQ72cmNC1PaIZ+DNqUpJdm9 TSt6434alSeWhJuvsn7ucXDQwIpbjZWh227uu20ZgLBbE7VjZsTwnxewFokgfb4EAJ LvLBQpi/G/1auNv4QQusGkXdU8JSZrePOkDViXQjlBRYQW+PugMVzhSWoArow0Etsq bvJCEg3u9HxW02NUKOzXIZu8WOCTskDQxzZ/xjtgbvvYnuj+M4TzFHobjRs9XaWRpH 2J58KnUQB999cRshiwnY7nvwvcdNYwP4ZB3jGLn7F3XM/ZL/pEssVEaN/14VN3WsH0 kjRAW9KizqnnA==
Am Thu, 6 Jan 2022 13:25:46 +0200
schrieb Eero Tamminen <oak@xxxxxxxxxxxxxx>:
> Hi Thomas,
>
> I noticed that you removed WinCE support.
>
> I removed the Hatari v1.x config examples for other constrained
> devices, as they're not supporting SDL2 either.
Good idea, thanks!
> Should the SMALL_MEM option be removed too?
I think we could remove it nowadays, yes - but actually I rather tend
to make SMALL_MEM=1 the default nowadays. Rationale:
- The huge STRam[16MiB] array is kind of ugly
- If we ever have a bug in one of the IO memory or ROM access
functions, it might be possible for a malicious Atari program to
access other variables in the BSS of Hatari (since they are in
well-known locations relatively to STRam[]) - if we malloc the memory
instead, the chances are way smaller that something ugly could happen
here beside crashing Hatari.
- I think the speed optimization that we get via the huge static
STRam[] array is completely neglectable on modern CPUs. Actually, I
just also did a completely unrepresentative benchmark by running
two Hatari instances in parallel and comparing their CPU usage with
"top", and the build with --enable-small-mem was even 0.3 % up to
1.0% better than the one without --enable-small-mem! Might be just
noise, of course, but at least there is no big difference between the
two modes.
So unless someone has some good objections, I think I'm simply going to
switch the code to use the SMALL_MEM behavior by default.
Thomas