[fpc-devel] Preparing 3.2.4, call for merge request and regressions

Christo Crause christo.crause at gmail.com
Sat Oct 2 21:09:25 CEST 2021

On Sat, Oct 2, 2021 at 7:42 PM Florian Klämpfl via fpc-devel <
fpc-devel at lists.freepascal.org> wrote:

> Am 01.10.2021 um 23:03 schrieb Christo Crause via fpc-devel <
> fpc-devel at lists.freepascal.org>:
> Below is a list of commits that kind of merge relatively easily.  This
> covers most of the relevant AVR patches up to Jan 2020, just before the
> avrtiny support was added.  There are three commits in this period that
> rely on more invasive and widespread changes of other commits, I will list
> them separately at the end.
> Thanks, applied.
> I needed also
> f92b8d1681c0d1ca2228b3114373085524cd93ff

Indeed, apologies for missing that one.

> Problematic - seems to require commits that affect other targets:
> 8fd0a27875abb2636a1388876f590a3a56d83b56 - commit doesn't compile, missing
> definition of labelcnt
> ae04e5d7f0c2527677b7c4ce6be2c235a4635c82 - doesn't compile, requires
> definition of TransferUsedRegs in 94d7a02fae1d06a40fc9313f7e42323f97d577c7
> but that doesn't merge cleanly (conflicts in aoptx86.pas).
> 4b4e316af02a968f27147123b189b04a9931ba79 - requires commit or fix that
> renames FPC_in_cpu_first to in_cpu_first
> If they do not fix really important things, then I would leave them out.

There are a couple of refactoring commits in the aopt units that seem like
general improvements (e.g. 94d7a02fae1d06a40fc9313f7e42323f97d577c7) which
haven't been picked yet.  Will these be merged at some point, maybe 3.4?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freepascal.org/pipermail/fpc-devel/attachments/20211002/2bef998b/attachment.htm>

More information about the fpc-devel mailing list