On 10/09/2017 02:08 PM, Sandra Loosemore wrote:
> On 10/09/2017 09:13 AM, Joseph Myers wrote:
>> The install.texi documentation for --disable-libssp only says "Specify
>> that the run-time libraries for stack smashing protection should not be
>> built.". I think it needs updating to mention these
On Mon, 9 Oct 2017, Sandra Loosemore wrote:
> On 10/09/2017 09:13 AM, Joseph Myers wrote:
> > The install.texi documentation for --disable-libssp only says "Specify
> > that the run-time libraries for stack smashing protection should not be
> > built.". I think it needs updating to mention these
This one.
https://gcc.gnu.org/ml/gcc-patches/2017-10/msg00537.html
There was discussion about documenting this, but the actual configure
change hasn't been reviewed yet.
-Sandra
On Mon, 9 Oct 2017, Sandra Loosemore wrote:
>> The install.texi documentation for --disable-libssp only says "Specify
> that the run-time libraries for stack smashing protection should not be
>> built.". I think it needs updating to mention these additional effects as
>> well.
> Oops. :") How ab
On 10/09/2017 09:13 AM, Joseph Myers wrote:
The install.texi documentation for --disable-libssp only says "Specify
that the run-time libraries for stack smashing protection should not be
built.". I think it needs updating to mention these additional effects as
well.
Oops. :") How about this
The install.texi documentation for --disable-libssp only says "Specify
that the run-time libraries for stack smashing protection should not be
built.". I think it needs updating to mention these additional effects as
well.
--
Joseph S. Myers
jos...@codesourcery.com
This patch allows you to configure GCC to explicitly (not) add
-lssp_nonshared -lssp link options when the -fstack-protector options
are provided, by overriding the inferred default setting for
TARGET_LIBC_PROVIDES_SSP. The specific use case this is for is a
bare-metal target where the runtime
