[RFC][PATCH] Refactoring FORTIFY
George Burgess IV
george.burgess.iv@gmail.com
Tue Oct 3 20:54:00 GMT 2017
I have not signed a copyright assignment yet, though I'm more than
happy to do so. Would
http://git.savannah.gnu.org/cgit/gnulib.git/plain/doc/Copyright/request-assign.future
be the appropriate form for me to fill out and send in?
If it changes things, I wrote this as a part of my work with Google,
who says they have a CLA on file with the FSF.
Thank you,
George
On Tue, Oct 3, 2017 at 12:34 PM, Adhemerval Zanella
<adhemerval.zanella@linaro.org> wrote:
> On 11/09/2017 03:26, George Burgess IV wrote:
>> Hello,
>>
>> Attached is a patch that aims to substantially improve FORTIFY's
>> usefulness with clang, and make defining FORTIFY'ed functions require
>> less ceremony.
>
> Due the patch size and complexity and no indication on the message, it
> would be good to know if you already have a copyright assignment, and
> if your work is covered by it.
>
> You will need it to sort this out first so someone can actually look
> into your patch (which I am interested in review btw).
More information about the Libc-alpha
mailing list