Re: [Freemint-discuss] Debugging a problem in gcc-14

[Miro K. <mir...@gm...>]

On Thu, 30 May 2024 at 14:25, Thorsten Otto <ad...@th...> wrote:

> On Donnerstag, 30. Mai 2024 13:02:03 CEST Miro Kropáček wrote:
>
> Hm, cannot agree:
>
I think you are still doing it wrong (or at least in a different way than I
meant). The most trivial way to do it:

- checkout https://github.com/gcc-mirror/gcc/tree/basepoints/gcc-14 --
that's the tag where gcc-14 development started. That means that at this
point it should still work for you (if not, do the same for
basepoints/gcc-13 and start from there)

- cherry-pick m68k-atari-mintelf commit(s) to this branch and call it e.g.
gcc-14-start

- checkout master into a separate branch, e.g. gcc-master-head

- rebase gcc-master-head on top of gcc-14-start

Result: you can start bisecting at gcc-14-start (good) and gcc-master-head
(bad) while your m68k-mintelf changes are there for all commits.

I have quickly verified that it all works without conflicts.

-- 
http://mikro.atari.org