This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [Bug build/7065] Support building glibc with -fstack-protector or -fstack-protector-all


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. (In any case, these days I
should be yelling 'VERIZON' which is much less fun.)

> commit 82f2eb623ce1d9bd0a4d2c45d9d47688e71ed383
> Author: Nick Alcock <nick.alcock@oracle.com>
> Date:   Tue Jun 7 12:06:16 2016 +0100
>
>     Enable -fstack-protector=* when requested by configure.

You realise that if applied in this order -- in particular, with this
commit preceding the ifunc one that hasn't landed on this branch yet --
the resulting branch will not be bisectable? Or at least it won't work
reliably if bisected...

You probably should reshuffle things later so that this commit lands
after all the others, whatever order they land in.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]