Posté le 04/03/2025 01:07
Planète Casio v4.3 © créé par Neuronix et Muelsaco 2004 - 2025 | Il y a 74 connectés | Nous contacter | Qui sommes-nous ? | Licences et remerciements
Planète Casio est un site communautaire non affilié à Casio. Toute reproduction de Planète Casio, même partielle, est interdite.
Les programmes et autres publications présentes sur Planète Casio restent la propriété de leurs auteurs et peuvent être soumis à des licences ou copyrights.
CASIO est une marque déposée par CASIO Computer Co., Ltd
Citer : Posté le 04/03/2025 08:54 | #
Hi! I'm not too surprised that the normal install doesn't work out-of-the-box... due to lack of testing mainly.
The TLB ERROR is hella suspicious. Getting the toolchain to build but getting a bad executable would be a first. Can you please report the full error (is there a PC value?) and attach a copy of the g3a?
(Your images didn't show up cause you put a link to a web page instead of the direct link to the image.)
Citer : Posté le 04/03/2025 09:03 | # |
Fichier joint
Hi,
Thank you for your swift response. I must note that I did remove all of the code from the main function, however the same error happened prior to this. Each time the TLB error reports exactly the same with target=0001000 and pc=00000498.
Citer : Posté le 04/03/2025 09:26 | #
Ok, I can reproduce. This System ERROR screen is from the OS which indeed strongly suggests that the crash happens before gint takes over. I'm gonna need to analyze the binary. Can I have a full copy of the project folder, build files included, please?
Citer : Posté le 04/03/2025 09:38 | # |
Fichier joint
Hi,
Here is an archive of the entire project folder.
Thanks.
Citer : Posté le 04/03/2025 10:06 | #
Hmm, nothing looks obviously suspicious (not like the previous time I've had a borked compiler anyway). I assumed you've installed the tools by cloning the repositories in order. What commits do you have for each of these? I wonder if this could be an oversight on my end with a bug remaining on the master branches, which sometimes happens because I live on dev mostly.
Now that I think about it you have GCC 15.0.1 but the GCC build for the fxSDK is 14.0.1. There could always be a hidden issue with this.
I suggest you try with the dev branches of fxSDK, gint and fxlibc first, which is the faster test, and if it doesn't work, maybe build GCC 14.0.1 following the sh-elf-gcc repository as closely as possible.
Citer : Posté le 04/03/2025 10:18 | #
I am on the latest commit at master on every repository. I followed the instructions on the repositories (adding certain other commands to work around building gcc with Xcode clang). I will try the dev branches then build GCC 14 and test it when I can, thank you.
Citer : Posté le 04/03/2025 14:07 | #
Hey,
I checked out the dev branches of every repository, compiled and installed them. Still received the same error. Recompiling everything with gcc 14 and using gcc 14 to build the addin it now runs on the calculator. Glad this works now, I wonder why GCC 15 does not work?…
Thank you for your help.
Citer : Posté le 04/03/2025 14:12 | #
Ok, I'm glad this is solved for now at least. The calculator runs on a SuperH CPU which is a bit obscure and doesn't receive much attention in GCC. When larges changes are made to the compiler it is possible for the SuperH backend to get subtle bugs that are not caught immediately. This has happened before, actually. IIRC GCC 15 is the version that added the post-register-allocation combine pass (basically a very late optimization) which broke many things at first. Maybe there is still some fallout.