@IamSONIC

You need to clean your SDK directory, completely. If you are using the native compiler from the FTP then I would not expect to see a single reference to clib2 in the path of the warning.

@IamSONIC
You are still building the sd2benchmark using clib2?

@Capehill

So, rather than building a new SDL2 I can just work around this issue by not calling that function?

Debug level 5. Nothing on serial at all.

Understandably not. I just wonder if you could make a v2.30.5-amigaos4 release with that fix?

@all
As a start, I have built a version of a cross-compiler and native-compiler; a pure GCC 6. There are no additional libraries right now.

Can someone test these. From there, I can add additional libraries. See post #1 for the links.

Makes sense.

You merged that directly into the latest release?

@Capehill
Thanks for quickly implementing something. Are you just stubbing out that function or are you planning on filling it in later? I ask wrt. commit https://github.com/AmigaPorts/SDL/comm ... 1e7d14451140fba6c4409d8b6

See: https://www.amigans.net/modules/newbb/ ... id=149822#forumpost149822. In this case, this is a successful demo where CLIB4 and SDL2 were not compiled with SPE flags at all.

It would be nice to good agreement or decisions as to whether or not
- we should be building C-libraries with the SPE flags in full, and whether
- we should be building SDL2 with SPE flags in full.

It would be nice to able to just do something like:

But as https://keasigmadelta.com/blog/taboriz ... imizing-for-the-e500-spe/ *bullet point 2* says, only critical code actually _using_ floats should be compiled with such flags in order to avoid the trashing of the ABI float parameters.

Presumably, we all need to be careful.

@IamSONIC
Yeah, I had a feeling that was the hack.

Binutils is slowly progressing, but I do not think it will be ready in.. say.. 2 or 3 months. I think that it realistically means still using Binutils 2.23.2 - at least GCC 6 is closer to that Binutils version that GCC 11.

@IamSONIC
The current native SDK compiler will not have any support for the clib4 value for the mcrt option. I am curious as to how you are bypassing it at all.

@capehill
Have you come across a situation where an SDL2 game with cause a freeze if either DEFAULT or COMPOSITING is selected as the renderer, but will work if anything else is selected?

I am seeing that I need to not choose DEFAULT or COMPOSITING for the latest version of the Wolf port otherwise something goes wrong in SDL_SetTextureScaleMode() causing an ISI error.

I am not particularly interested in drilling down and debugging for hours so I would rather just bypass it. What is the best way to bypass it so that the user does not manually have to set the RENDER DRIVER in the SDL prefs app? Just invoke SDL_SetHint(). The issue with that is that I would need to set it back to the original value, which is fine, but if the program ends early then setting it back may not happen. It is not the cleanest thing. I could also immediately set it back after initialisation, but I am not sure if it should stay as the hacked value throughout the duration of the game.

@capehill
wrt. batching: Looking at SDL_render.c, there are times where it can be set to FALSE. I guess there is no downside to just using the SDL prefs tool and forcing batching always?

@Hans
Right now, we are limited to GCC6.

Calling on those working on developing for the A1222:

Is there anything currently holding you back?

I know that @Stefen.H was lacking an SPE compiled version of some thing that he would like.

Perhaps this thread can stick to A1222 development topics and requests for people. Over at our team (AmigaLabs: https://amigalabs.net/ || https://github.com/AmigaLabs) we can probably help if a specific build of a library or a specific cross compiler is required. Like anyone else - we have the ability to build a cross compiler and/or native compiler that is SPE ready. It would also be possible to bundle up a ready-to-go cross compiler/native compiler (gcc6 SPE) + compiled-with-SPE libraries.

Any issues right now?
Any requests?

=== OFFICIAL DOCKER ===
= Images:
https://hub.docker.com/repository/dock ... /amigagccondocker/general

= Repository:
https://github.com/walkero-gr/AmigaGCConDocker

=== EXPERIMENTAL STANDALONE FTP SDK ===
The following should contain a Linux cross compiler and compatible native compiler to be used on AmigaOne machines:
FTP: tellusregio.duckdns.org
PORT: 32463
USER: ftp / ANONYMOUS login.

Inside the LHA files, see the file named "RJD_README.txt" which declares the version of ADTOOLS and CLIB4.

It should be noted that the FTP SDK is separate to the Docker images and it is experimental.

=== Things that are not clear right now ===
- See https://www.amigans.net/modules/newbb/ ... id=149824#forumpost149824 (i.e. Whether or not building an entire project with SPE FLAGS is a good idea)

The following is a list of helpful links that I will keep up to date.
*** If you want to a link below, let me know in this thread or by private message. ***

=== Links ===
- https://keasigmadelta.com/blog/taboriz ... imizing-for-the-e500-spe/ (Hans de Ruiter)
- https://www.amigans.net/modules/newbb/ ... &order=ASC&status=&mode=0 (Eldee Stephens)
- https://www.amigans.net/modules/newbb/ ... 8&start=40&post_id=147271 (Walkero)

@all

Batch mode optimization... is this default or must it be programmed?

@capehill

Do you expect any changes between this latest RC and the actual 2.30.4 release?

@AmigaOldskooler

You busy with life? I didn't see a monthly update or am I too eager?

@dfstudios
https://www.amigans.net/modules/newbb/ ... &order=ASC&status=&mode=0

I also found the Enhancer version to have problems. I appreciate what they do, but generally stick to the original tools if they are not broke.