On Sat, 2024-12-14 at 18:34 -0500, David Malcolm wrote: > On Sat, 2024-12-14 at 10:11 +0000, Sam James wrote: > > David Malcolm <dmalc...@redhat.com> writes: > > > > > On Thu, 2024-12-12 at 12:56 -0500, James K. Lowden wrote: > > [...] > > > > > > > > > Thank you for your kind consideration of our work. > > > > > > Please forgive me if you've already said this elsewhere, but is > > > this > > > work available in a public git repo somewhere? > > > > > > > https://gitlab.cobolworx.com/COBOLworx/gcc-cobol/ > > > > > > Thanks Sam. I was able to clone and build from that repo on x86_64- > pc- > linux-gnu (building with gcc 10) and have now compiled my first ever > COBOL program! >
[...snip...] > Taking it for a test-drive; thanks! > Dave James: Looking at ./gcobol --version I see: gcobol (GCC) 15.0.0 20240828 (experimental) which makes it look like the last time you refreshed your branch from master was 3.5 months ago. Looking in your git repo here: https://gitlab.cobolworx.com/COBOLworx/gcc-cobol/-/commit/6fc49cbd858adfbd689ebe45eb631a4eacbc9288 I see: Merge remote-tracking branch 'gnu-gcc/trunk' into bobdev parents 5d165a3d 898f013e so it looks like 898f013e195fa828bb30ae6ba4ad50abbd804fbd aka: r15-3264-g898f013e195fa8 is the most recent commit on master that this work is based on top of, unless I missed a later merge. Is that the baseline that the patches you sent was based on? It's probably a good idea to do a refresh before the next iteration of the patches, given that we're now on r15-6258-g3e343ef7f0ac0e i.e. almost 3000 commits later (this is the output of ./contrib/git-descr.sh , in case you're not familiar with this tool, which gives us nice sequential numbering for commits). Hope this is helpful Dave
