FastCode: Difference between revisions

Revision as of 19:44, 31 July 2025

Revision as of 19:40, 9 August 2025

Line 11:

The project enjoys the support of Embarcadero who recognizes the contributions of the FastCode team and incorporates their code into the codebase for Delphi.<ref>{{cite web|url=http://blogs.embarcadero.com/nickhodges/2006/11/27/29891|title=Nick Hodges|publisher=|accessdate=3 September 2015}}{{Dead link|date=July 2025 |bot=InternetArchiveBot |fix-attempted=yes }}</ref> The default [[memory management|memory manager]] for [[Embarcadero Delphi]], FastMM4, is the winner of the FastCode Memory Manager challenge.<ref name="embarcadero.com">{{cite web|url=http://blogs.embarcadero.com/abauer/2005/09/28/21433|title=The Oracle at Delphi|publisher=|accessdate=3 September 2015|archive-date=12 August 2015|archive-url=https://web.archive.org/web/20150812002619/http://blogs.embarcadero.com/abauer/2005/09/28/21433|url-status=dead}}</ref>

The project was first hosted on Robert Lee's [[OptimalCode]] site, and its source code's home page is [httphttps://fastcode.sourceforge.net/], last updated in 2008. The source code contains both the enhanced routines and the testing suites to benchmark the routines. In 2017, the benchmark routines for Move, FillChar and the memory manager have been ported for 64-bit, available at [https://github.com/maximmasiutin/FastCodeBenchmark].

== Testing ==

Line 28:

== List of challenges ==

The FastCode project has run the following challenges [httphttps://fastcode.sourceforge.net/]:

{{Div col|colwidth=22em}}

*AES ([[Advanced Encryption Standard]])

Line 107:

== The FastCode Library ==

All the challenge winners are included in the FastCode library (httphttps://fastcode.sourceforge.net/challenge_content/rtl_replcmnt_pkg.html). This library is [[Open-source software|open source]], released under the [[Mozilla Public License|MPL license]]. The library can be used in two ways: 1) calling functions directly, and 2) using the patching functionality.

When calling functions directly it is entirely up to the application developer to call the version of a function he thinks is fastest.