|[hatari-devel] DSP question|
[ Thread Index |
| More lists.tuxfamily.org/hatari-devel Archives
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: [hatari-devel] DSP question
- From: Douglas Little <doug694@xxxxxxxxxxxxxx>
- Date: Fri, 31 Jul 2015 13:53:47 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=ITNOKaAnx6wbk5Wlvvl5uIuli1IpyIGkp2jS4H2yQFk=; b=I1lf5I91ut70y6GC3T0Z3amGBxRB5ehz+Nr9ok168tUm12+x9p3+1hqSvLoGgGEWVG mPQGh4fgf/DcfMTKTIMnPgwcSHu9bgCDdCifhlRhbHqT46W4ukU8/Wtz/uvg1a2y0HGI aS3fozkivkMgJHPfmJBkdsukUndH6+1A02IYDRh3A5J4s/GQAKlnRRfrAINnHMkgoEEj 1gbqdgJts/GNSh1jVf0+sCKx5MySXEzXICsxK0ILTHq09nArjDGPb6osth1la1HEq93I HtVjpbyNgiiWhMSZhfLpe5X0dHDw2InUMuE8puIPG4JVVoh5Ohapq8KkQ6LqkYIKCYk0 bQVQ==
Does anyone know if the CCR saturation arithmetic / limit flag is implemented in Hatari?
i.e. when a 56bit accumulator is stored to some 24bit destination, overflows result in saturation and the L bit is set in the CCR and remains sticky until cleared.
I'm seeing some indication that the L flag is not being set - or if it is set, the JLS jump condition is ignoring it (although I'll need to test it more carefully to be 100% sure).