This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] review request: implementing DW_AT_endianity
- From: Peeter Joot <peeter dot joot at gmail dot com>
- To: Tom Tromey <tom at tromey dot com>
- Cc: gdb-patches at sourceware dot org, Peeter Joot <peeter dot joot at lzlabs dot com>, Simon Marchi <simark at simark dot ca>
- Date: Wed, 13 Feb 2019 09:11:23 -0500
- Subject: Re: [PATCH] review request: implementing DW_AT_endianity
- References: <VI1PR0501MB286163B3EC58E11776F29D2A9C750@VI1PR0501MB2861.eurprd05.prod.outlook.com> <20171010233010.58471-1-peeter.joot@lzlabs.com> <87371tq6uz.fsf@tromey.com> <CAJ4e__gakTnAPc9dN01EXF+pT43DMdZBJQKYNPYGra7RW5sAtQ@mail.gmail.com> <87sgwr6de7.fsf@tromey.com>
> Hi! What is the status of this? I'm still interested in getting this
> patch into gdb.
>
Hi Tom,
FSF legal is essentially unresponsive about the contribution paperwork that
we submitted (Oct 2017.)
We last heard from the FSF Licensing & Compliance Manager August 31st last
year, who stated they were hiring a new administrator, and asked for some
time to review. Our company legal asked if we could provide any additional
information to help things along Oct 1st last year, and again Jan 14th this
year -- I don't believe we received any reply from the FSF.
The delays were so extensive that we've opted to use lldb as our backend
debugger, and have started contributing changes to the lldb/clang/llvm
stack instead. That said, if the FSF does process our contribution
paperwork, it is still my intention to rebase my changes against
binutils/LATEST and submit a patch.
--
Peeter