This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [Bug build/7065] Support building glibc with -fstack-protector or -fstack-protector-all
- From: Nick Alcock <nick dot alcock at oracle dot com>
- To: Florian Weimer <fweimer at redhat dot com>
- Cc: libc-alpha at sourceware dot org
- Date: Fri, 29 Jul 2016 14:30:16 +0100
- Subject: Re: [Bug build/7065] Support building glibc with -fstack-protector or -fstack-protector-all
- Authentication-results: sourceware.org; auth=none
- References: <bug-7065-9157@http.sourceware.org/bugzilla/> <bug-7065-9157-7r08lfCGxG@http.sourceware.org/bugzilla/> <87zip1mmtm.fsf@esperi.org.uk> <a5702254-a74d-d52e-57e0-fda9b4ac02c3@redhat.com> <87r3acivh0.fsf@esperi.org.uk>
[Resend after sourceware spamblocked me, sorry for the duplicate; I'm
using the same Message-ID, which might help]
On 29 Jul 2016, Florian Weimer uttered the following:
> On 07/28/2016 06:15 PM, Nick Alcock wrote:
>> On 28 Jul 2016, cvs-commit at gcc dot gnu org said:
>>
>>> https://sourceware.org/bugzilla/show_bug.cgi?id=7065
>>>
>>> --- Comment #20 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
>>> This is an automated email from the git hooks/post-receive script. It was
>>> generated because a ref change was pushed to the repository containing
>>> the project "GNU C Library master sources".
>>>
>>> The branch, fw/stack-protector has been created
>>
>> Jumping around the room going 'YAHOO!' is not professional so of course
>> I did not do that when this email arrived.
>
> Sorry, this is a misunderstanding. I just pushed it to a private branch because Kostya wanted to look at the patch series because
> we suspect the places which need Address Sanitizer opt-out are quite similar.
Ah, OK. I did think it was actually still mostly private, but it's sort
of more real now it's on a private branch in the right git repo. :)
(Though you might be able to asan more of ld.so rather than just running
away from that problem like I did.)