public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Joseph Myers <joseph@codesourcery.com>
To: Nix <nix@esperi.org.uk>
Cc: <libc-alpha@sourceware.org>, <carlos@redhat.com>
Subject: Re: [PATCH 01/12] Configury support for --enable-stack-protector.
Date: Sat, 20 Feb 2016 17:30:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.10.1602201729590.7140@digraph.polyomino.org.uk> (raw)
In-Reply-To: <1455963826-21885-2-git-send-email-nix@esperi.org.uk>

Any patch adding a new configure option should also document it in 
install.texi and regenerate INSTALL.

-- 
Joseph S. Myers
joseph@codesourcery.com

  parent reply	other threads:[~2016-02-20 17:30 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-20 10:23 --enable-stack-protector for glibc Nix
2016-02-20 10:23 ` [PATCH 04/12] Allow overriding of CFLAGS as well as CPPFLAGS for rtld Nix
2016-02-20 10:24 ` [PATCH 03/12] Initialize the stack guard earlier when linking statically Nix
2016-02-20 10:24 ` [PATCH 06/12] Compile the entire dynamic linker with -fno-stack-protector Nix
2016-02-20 10:24 ` [PATCH 08/12] Link various tests " Nix
2016-02-20 10:24 ` [PATCH 01/12] Configury support for --enable-stack-protector Nix
2016-02-20 10:44   ` Andreas Schwab
2016-02-20 12:03     ` Nix
2016-02-20 13:10       ` Andreas Schwab
2016-02-20 15:04     ` Nix
2016-02-20 17:30   ` Joseph Myers [this message]
2016-02-21 12:40     ` Nix
2016-02-21 22:31     ` Nix
2016-02-22 18:03       ` Joseph Myers
2016-02-22 21:23         ` Nix
2016-02-20 10:24 ` [PATCH 07/12] Link libc.so with libc_nonshared.a to pull in __stack_chk_fail Nix
2016-02-20 10:25 ` [PATCH 05/12] Mark all machinery needed in early static-link init as -fno-stack-protector Nix
2016-02-20 10:25 ` [PATCH 09/12] Enable -fstack-protector=* when requested by configure Nix
2016-02-20 10:25 ` [PATCH 10/12] Work even with compilers hacked to enable -fstack-protector by default Nix
2016-02-20 17:32   ` Joseph Myers
2016-02-21 15:11     ` Nix
2016-02-20 10:25 ` [PATCH 11/12] Drop explicit stack-protection of pieces of the system Nix
2016-02-20 10:25 ` [PATCH 12/12] Avoid stack-protecting certain functions called from assembly Nix
2016-02-20 10:25 ` [PATCH 02/12] Make __stack_chk_fail() not use other glibc facilities Nix
2016-02-20 12:06   ` Nix
2016-02-20 17:19     ` Mike Frysinger
2016-02-21 12:44       ` Nix
2016-02-22  1:20         ` Mike Frysinger
2016-02-22 12:32           ` Nix
2016-02-22 19:45       ` Nix
2016-02-20 17:36   ` Joseph Myers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.10.1602201729590.7140@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=carlos@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=nix@esperi.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).