On Tue, Jul 29, 2025 at 5:48 AM Robert Dubner <rdub...@symas.com> wrote: > > It takes a village. > > Specifically, it took a village for me to accomplish the goal of possibly > bringing the COBOL front end in the next release of GCC-15 up to the > current level found in GCC-16. > > I can't thank Richard and Jakub and Thomas and the group here enough. I > came in knowing nothing, and you kept guiding me as I fumbled about > accumulating knowledge. And it appears to have worked, and through it I > have learned a bunch about GIT that I simply didn't know existed. > > The generosity of this communitry is an ongoing amazement. > > I believe that I have checked all of the boxes that Richard told me about. > > For the record, here are the commands that created the "patch": > > ============ > > $ git switch -C patched15 gcc/releases/gcc-15 > > $ git cherry-pick -x --allow-empty --allow-empty-message > --keep-redundant-commits \ > $(git rev-list --reverse basepoints/gcc-16..gcc/master \ > --invert-grep --grep="Daily bump" \ > --invert-grep --grep="Malcolm" \ > -- libgcobol gcc/cobol gcc/testsuite/cobol.dg ) > > ============ > > The result of that is the branch "patched15". It has 47 cherry-picked > commits on top of gcc/releases/gcc-15. With gcc-15.1.0 as the compiler, > it successfully compiles on an x86_64-linux Ubuntu 22.04 LTS system > starting from "../configure --enable-languages=all,cobol", meaning it is a > bootstrapped multilib build. "make check-cobol" then runs with no > unexpected errors. > > That branch "patched15" can be found at > https://gitlab.cobolworx.com/COBOLworx/gcc-cobol.git.
That looks good apart from the pick of 0eac9cfe which brings in unrelated c/c++ frontend changes for a gcobolspec.cc change. This rev should be skipped. You can edit it out with a git rebase -i for example. > I respectfully request that it be considered for merging into > releases/gcc-15. Fine with me otherwise. Thanks, Richard. > Thanks again. > > Bob Dubner > > >
