I run into the same problems since most of my merge requests are focused on optimisation of generated assembly language, which does require a very careful eye to verify, and even then edge cases can sometimes still get through.

Recently I've been working on compiler features, namely pure functions and vectorisation.  The vectorisation one has a potential code flow problem but I think was necessary due to how SIMD registers work on x86, but as a result is currently sitting in limbo.  And pure functions have been sitting around for 2 years, and developed over 2 years before that!  I would like it merged into the trunk so I can start development of the next stage - the ability to assign the results of pure functions to constants - but it itself is waiting on a merge request that overhauls the Currency type to be more internally consistent in the compiler so constant propagation works properly on it.

As much as I want to say "Just trust me, bro" and have them merged, that tends not to fly in software development circles!! Granted, I do wonder if, with some things, it's worth merging them and then fixing the teething problems as they arise.

Kit

On 03/04/2026 09:17, Michael Van Canneyt via fpc-devel wrote:


On Fri, 3 Apr 2026, Graeme Geldenhuys via fpc-devel wrote:

Hi,

I don't know the FPC development process, so was wondering if 134 open merge requests are considered "normal" for this project? Some MRs are as old as 5 years. 😬

https://gitlab.com/freepascal.org/fpc/source/-/merge_requests

I consider it by no means "normal".

But verifying takes time and we're dramatically short on manpower.

What I can judge, I try to resolve as quickly as possible.
Compiler-related merges in general fall outside my competence zone, so I seldom touch them (apart from adding the category label).

Michael.

_______________________________________________
fpc-devel maillist  -  [email protected]
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
_______________________________________________
fpc-devel maillist  -  [email protected]
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Reply via email to