News:

Herr Otto Partz says you're all nothing but pipsqueaks!

Main Menu

Compatibility issue

Started by stanceboyCZ, September 30, 2025, 05:22:08 PM

Previous topic - Next topic

stanceboyCZ

Hey guys, almost all of the tools and programs for Stunts are not for 32-bit. And i request you guys to do it compatible.

Matei

I have 32-bit tools:

https://matei.one/idxscr.html

Besides the games, there's a  program for viewing tracks from Stunts in simcarstunts-6.0.4.tar.gz. I always compile the versions for wind0w$ with Open Watcom 1.9, so they are 32-bit. I still recommend that you install some GNU/Linux though and let's not forget that your CPU is 64-bit. My chess game is also 32-bit:

https://matei.one/idxchess.html

 

Duplode

@stanceboyCZ At the moment, which tool or tools you'd like to have a 32-bit executable, so that we can look into preparing it?

(For my tools in particular, I haven't been making 32-bit binaries because I no longer use 32-bit systems, and also because some relevant toolchains are gradually dropping 32-bit support. Still, I could try to work it out using a VM or some such.)

Matei

https://en.wikipedia.org/wiki/Haskell

QuoteThe Glasgow Haskell Compiler (GHC) compiles to native code on many different processor architectures, and to ANSI C, via one of two intermediate languages: C--, or in more recent versions, LLVM (formerly Low Level Virtual Machine) bitcode.

So where's the problem?

Duplode

Quote from: Matei on Yesterday at 10:00:34 AMSo where's the problem?

-fvia-c isn't really a practical option for compiling one's everyday programs. See https://downloads.haskell.org/ghc/latest/docs/users_guide/codegens.html#c-code-generator-fvia-c :

QuoteThis is the oldest code generator in GHC and is generally not included any more having been deprecated around GHC 7.0. Select it with the -fvia-C flag.

The C code generator is only supported when GHC is built in unregisterised mode, a mode where GHC produces "portable" C code as output to facilitate porting GHC itself to a new platform. This mode produces much slower code though so it's unlikely your version of GHC was built this way. If it has then the native code generator probably won't be available. You can check this information by calling ghc --info (see --info).