"James K. Lowden" <jklow...@schemamania.org> writes: > On Thu, 12 Dec 2024 12:56:36 -0500 > "James K. Lowden" <jklow...@schemamania.org> wrote: > >> The following 8 patches constitute the 80 files needed to build and >> document the COBOL front end. > [...] > * does not build on Darwin/macOS [Iain] > [...] > - 32-bit architectures are not a consideration.
As Joseph said then, if that's the case, configure work will be needed to not regress --enable-languages=all on such platforms. > > * building on the compile farm? [Iain] > - No, don't know how yet. Willing. > > * does your testing include bootstrap builds? [David] > - No, we normally use > --disable-bootstrap > --disable-multilib Please do at least one bootstrap build at least before resubmitting. Ideally have a CI job which runs at least nightly for bootstrapping. > > * How would it be regression tested? [Andi] > - need to discuss licensing and feasibility > (I really believe this is a must. Not least because middle-end or backend changes could regress COBOL and we want to detect that.) > * ideal would be a branch with just the 8 patches [Iain] > - I test the patches on the cobol-patched branch, but I don't normally > push them. Iain is asking for you to push them to a branch temporarily to make it easier to fetch and review, given the submission issue here (with not using git-send-email or similar). > [...] > == Infeasible == > > * Please use `git send-email` with threading. [Sam] > - dev machines have no email > You can use `git format-patch` to create send-email-able patches and then run `git send-email` on another machine. Or you can attach the output of `git format-patch` in your usual mail client. You are not required to use `git send-email` *itself*, but you do need to submit patches in a well-formed way. Note that git send-email doesn't require sendmail or something running locally, it can be given an SMTP server to speak to.
