Re: vax binutils 2.39 gas problems
"Maciej W. Rozycki" <[email protected]>
| Newsgroups | gmane.os.netbsd.ports.vax,gmane.os.netbsd.devel.toolchain |
|---|---|
| Message-ID | <[email protected]> |
Christos -- On Fri, 27 Jan 2023, Christos Zoulas wrote: > > On Jan 27, 2023, at 7:44 PM, Izumi Tsutsui <[email protected]> wrote: > > > > christos@ wrote: > > > >> I think I found the problem.... > > > > Thanks, with the following your commit > > https://mail-index.netbsd.org/source-changes/2023/01/27/msg143037.html > > now vax bootloader builds. Do you have plans to submit your fix upstream? Preferably with a GAS test case (I can help you with that) reduced from the original problematic assembly source. The VAX port has so little target-specific coverage in the testsuite and without that it's hard to track quality; we don't know what the reference is even. Please note that it's not necessary anymore to assign the copyright of the FSF to contribute to upstream binutils (cf. binutils/MAINTAINERS): -------------------------------------------------------------------------- The alternative is to sign off the contribution by agreeing to the Developer's Certificate of Origin (version 1.1 or later) and adding a line to the end of the contribution that looks something like this: Signed-off-by: Random J Developer <[email protected]> The details of the Developer's Certificate or Origin can be found here: https://developercertificate.org/ -------------------------------------------------------------------------- With the requirement for copyright assignment lifted I do encourage you to contribute any local changes you may have so as to save everyone duplicate effort. Maciej