Forum > Lazarus

Lazarus Release 2.2.0

(1/14) > >>

The Lazarus team is glad to announce the release of Lazarus 2.2.

This release was built with FPC 3.2.2.

Here is the list of changes for Lazarus and Free Pascal:

Here is the list of fixes for Lazarus 2.2.x:

The release is available for download on SourceForge:

Choose your CPU, OS, distro and then the "Lazarus 2.2.0" directory.

Checksums for the SourceForge files:

Minimum requirements:

   2k, XP, Vista, 7, 8, 8.1 and 10, 32 or 64bit.

   gtk 2.8 for gtk2, qt4.5 for qt, qt5.6 for qt5, 32 or 64bit.

Mac OS X:
   Cocoa (64bit) 10.12 to 11.4, Carbon (32bit) 10.5 to 10.14, qt and
   qt5 (32 or 64bit).

The gitlab page:

For people who are blocked by SF, the Lazarus releases from SourceForge are mirrored at:

Wow, can I be the first to thank and congratulate the team for this great work ?


Long awaited, thank you very much! Will try immediately.

Please keep up the great work.

As a side note:

For x86_64,both FPC 3.2.0 and FPC 3.2.2 have a bug in the optimizer.

From current observation this issue is extremely rarely triggered. However, if the IDE for x86_64 is compiled with O2 or higher, then at least FpDebug will be broken (The affected code is a generic in LazUtils: TLazThreadedQueue or TLazFifoQueue).
Other parts of the IDE have not yet been observed, however even if the bug is in effect, the broken code needs to be executed with very specific arguments. Therefore, actual faulty behaviour could occur rather seldom. Yet, as any bug, it can strike at any time.

Compiling with -O1 is save
Compiling with -O2 -OoNoPeepHole  should also be save..

It is recommended for x86_64 users, to build your IDE with -O1 only.

This issue also affects 2.0.x (or potentially other code) if build with 3.2.0 or 3.2.2.
Since the triggers for this issue (complier going wrong, and resulting broken code actually failing) are extremely complex, not every IDE build (with 3.2.0/2 and -O2 up) will immediately show symptoms. It is possible that an affected build runs without issues, or fails once every few month only.

As for your own projects, you need to come to your own decision.  I have not seen any reports of this issue (other for the IDE), and 3.2.0 has been out for a good time.
Yet, no guarantees.

The issue is fixed in 3.2.3, so with the upcoming 3.2.4 this problem will be gone.

32 bit users should not be affected by this.
Non intel platforms should also not be affected.

Nice, thanks  :)


[0] Message Index

[#] Next page

Go to full version