Firenzina 2.4.3 xTreme

Discussion of anything and everything relating to chess playing software and machines.

Moderators: hgm, Rebel, chrisw

Gusev
Posts: 1476
Joined: Mon Jan 28, 2013 2:51 pm

Firenzina 2.4.3 xTreme

Post by Gusev »

Unfortunately, wikispaces have shut down firenzina.wikispaces.com, so I chose to make Firenzina 2.4.3 xTreme for modern Windows computers available at http://www.firenzina.org/Firenzina_2-4- ... -01-27.zip. This version is a result of porting the improvements made from 2.4 to 2.4.1 into 2.3.1. My tests show between +3 and +6 Elo improvement, no big deal. Firenzina is an open-source fork of Fire 2.2 based on Ippolit.
stevenaaus
Posts: 608
Joined: Wed Oct 13, 2010 9:44 am
Location: Australia

Re: Firenzina 2.4.3 xTreme

Post by stevenaaus »

Where is the source ?
I pulled from https://github.com/Censor/Firenzina , but it still shows 2.4.1
JoshPettus
Posts: 730
Joined: Fri Oct 19, 2012 2:23 am

Re: Firenzina 2.4.3 xTreme

Post by JoshPettus »

Hi Dmitri,

I had sent a pm to Kranium for 2.4.1 to fix compiling on OSX. I don't know if he got it, or if it's relevant for 2.4.3. I don't see the code either. :)

In utility.c, get_nprocs isn't a function in OSX. So after some searching around, I found a way to define it for osx. There is probably a cleaner way to do it, but at least it works.

https://www.dropbox.com/s/s1zd4t3yeid2p ... patch?dl=0

Regards,
Josh
Gusev
Posts: 1476
Joined: Mon Jan 28, 2013 2:51 pm

Re: Firenzina 2.4.3 xTreme

Post by Gusev »

This is an unplanned release, thank you for the reminder! I made the sources available at http://www.firenzina.org/Firenzina_2-4-3_sources.zip. These sources do not contain the code added to 2.4.1 to port it for Android. Also, the 2-4-3 branch of the GitHub does not contain the right code, please disregard it.
Gusev
Posts: 1476
Joined: Mon Jan 28, 2013 2:51 pm

Re: Firenzina 2.4.3 xTreme

Post by Gusev »

Hi Joshua,

I apologize for the inconvenience caused by the change of policy by wikispaces! Thank you very much for your contribution! Unfortunately, I don't have a single OSX device at my disposal. :(

Dmitri
stevenaaus
Posts: 608
Joined: Wed Oct 13, 2010 9:44 am
Location: Australia

Re: Firenzina 2.4.3 xTreme

Post by stevenaaus »

Gusev wrote:This is an unplanned release, thank you for the reminder! I made the sources available at http://www.firenzina.org/Firenzina_2-4-3_sources.zip. These sources do not contain the code added to 2.4.1 to port it for Android. Also, the 2-4-3 branch of the GitHub does not contain the right code, please disregard it.
46 MB download for source !?!
I can't do that right now :oops: . If you could make it reasonable, i can also test out the OS X patch. Thanks
Gusev
Posts: 1476
Joined: Mon Jan 28, 2013 2:51 pm

Re: Firenzina 2.4.3 xTreme

Post by Gusev »

Hi Steven,

wikispaces kindly agreed to revive the Firenzina wiki, so the much smaller version of sources for Firenzina 2.4.3 (without *.obj files etc.) is now available at http://firenzina.wikispaces.com/file/vi ... ources.zip.

Dmitri
stevenaaus
Posts: 608
Joined: Wed Oct 13, 2010 9:44 am
Location: Australia

Re: Firenzina 2.4.3 xTreme

Post by stevenaaus »

Thanks :)
Goes well on Linux, but it has some linkage/ifdef problems for me on OS X (10.8)
Gusev
Posts: 1476
Joined: Mon Jan 28, 2013 2:51 pm

Re: Firenzina 2.4.3 xTreme

Post by Gusev »

See if these problems can be alleviated by starting with the "2.4.4" development branch at https://github.com/Censor/Firenzina. Right now it's just a replica of 2.4.1 with a changed version number: I don't have separate numbering for development versions like Stockfish does. (Not yet.) If you succeed, then I'll be happy to accept a pull request for that newly created GitHub branch. Please make sure that all OS X specific things are guarded by appropriate ifdefs so compatibility with other platforms is not affected.
JoshPettus
Posts: 730
Joined: Fri Oct 19, 2012 2:23 am

Re: Firenzina 2.4.3 xTreme

Post by JoshPettus »

I did put ifdef __Apple__ and if def __linux__ in the patch. Things got moved around apparently in 2.4.3, but you can still put the code in manually. Look for get_nprocs It compiles after that. All I did was put in a little section defining it for OSX.