From: Nix <nix@esperi.org.uk>
To: Richard Henderson <rth@redhat.com>
Cc: Jack Howarth <howarth@bromo.msbb.uc.edu>, gcc@gcc.gnu.org
Subject: Re: does -fstack-protector work for gcc 4.1 on Darwin 8?
Date: Mon, 08 Aug 2005 22:48:00 -0000 [thread overview]
Message-ID: <87hde0hwox.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <20050804034851.GB18262@redhat.com> (Richard Henderson's message of "4 Aug 2005 04:50:56 +0100")
On 4 Aug 2005, Richard Henderson whispered secretively:
> On Wed, Aug 03, 2005 at 09:39:13PM -0400, Jack Howarth wrote:
>> Do you think I should be able to build gcc itself with the
>> -fstack-protector flag and what is the most appropriate way to
>> achieve that (ie brute force using a CFLAG or some configure
>> flag)?
>
> Considering that I don't think that self-building with
> -fstack-protector will ever be common, I don't think we
> ought to spend too many brain cells on this.
It was always possible with the SSP implementation, FWIW.
(This was useful to get a libgcc compiled with -fstack-protector,
although it's true that changing the TCFLAGS in gcc/Makefile
also lets you do that.)
> The only way to bootstrap with -fstack-protector without
> existing support in libc is to use a top-level bootstrap.
... which is reasonable, I think. (This was also true of
SSP.)
--
`Tor employs several thousand editors who they keep in dank
subterranean editing facilities not unlike Moria' -- James Nicoll
next prev parent reply other threads:[~2005-08-08 22:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-04 1:42 Jack Howarth
2005-08-04 3:50 ` Richard Henderson
2005-08-08 22:48 ` Nix [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-04 5:18 Jack Howarth
2005-08-04 1:15 Jack Howarth
2005-08-04 0:52 Jack Howarth
2005-08-04 0:54 ` Eric Christopher
2005-08-04 1:03 ` Richard Henderson
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=87hde0hwox.fsf@amaterasu.srvr.nix \
--to=nix@esperi.org.uk \
--cc=gcc@gcc.gnu.org \
--cc=howarth@bromo.msbb.uc.edu \
--cc=rth@redhat.com \
/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).