Re: [MiNT] XaAES sources for FreeMiNT 1.16.3

[Paul Wratt <paul.wratt@gmail.com>]

2009/12/8 Vincent Rivière <vincent.riviere@freesbee.fr>:
> Paul Wratt wrote:
>>
>>  .. it appears to be mintara.prg, if possibly only on certain
>> hardware, which does not explain why 1.16 is fine
>
> You use Alan's build. It's OK for me in text mode. As I'm unfamiliar with
> XaAES stuff, I never tried graphics mode.
>
> Alan's builds usually use the "enhancements" branchs. That can make some
> difference.
>
> And if I'm not wrong, Alan uses GCC 4.x. There is maybe a compiler issue.
> Some existing hidden bugs appears when changing the compiler, or when
> compiling at high optimization levels. The biggest source of problems can be
> the "strict aliasing rule", or assembly routines that forgot to backup some
> registers.
>
> The first step should be that someone is able to reproduce your problem. If
> you zip your ARAnyM setup and make it available for us, we will tell you
> quickly if we encounter the bug or not.
>
> --
> Vincent Rivière
>
Sorry it took so long, you can get "for-AFROS-test.zip" here:
http://sourceforge.net/projects/afros-update/files/
or a direct link here:
http://sourceforge.net/projects/afros-update/files/for-AFROS-test.zip/download

I double checked both the screen shot issue with new build, and
"invalid pixel format" on standard 1.17 on LiveCD.

see the readme for system replication.

I can reproduce these issues with both LiveCD and current 0.9.9 on my
Linux, the results are the same.

I suggest that anyone here who uses ARAnyM and wants to check for
"invalid pixel format", if you can get Gradient rendering with your
current 1.17 (dated AFROS 8.12 or greater), you will never get this
problem. But please test the supplied 1-17-cur for dialog and desktop
rendering issue (as per screenshot above)

Paul