[fpc-devel] 64bit win dwarf differences between fpc 2.4.2 and trunk

[Marco van de Voort]

In our previous episode, Vincent Snijders said:
> Also I noticed that some revisions are not on that list, for example
> r14068, probably because it is blocked, but its changes in dbgbase are
> used in later revisions. So I got stuck.

I blocked some large revisions (and afaik Jonas has in the past too),
because such feature branch merges (that rev is obj-p) will never be merged,
and if so, then upset mergetracking is the least of the problems.

> What would be the best way to proceed to identify the fixes in fpc
> 2.5.1 for DWARF info to be included in fpc 2.4.3 or a patched fpc
> 2.4.2?

Basically reviewing every commit to trunk since fixes_2_4 branching. It
should be easy to check against a fixes_2_4 commit log, since that one
doesn't contain that many commits to compiler/ (beware of lnfodwarf though).

So

svn log -v on trunk for the range (branchpoint - now), filter for commits to
compiler/ 

same for fixes, but then use this output to select two hands of commits that
actually touch compiler/

the difference is the raw list of unmerged changes to the compiler.

(filter makefile fixes and commits to compiler/utils also to avoid garbage)