From: Richard Henderson <rth@redhat.com>
To: Jack Howarth <howarth@bromo.msbb.uc.edu>
Cc: gcc@gcc.gnu.org
Subject: Re: does -fstack-protector work for gcc 4.1 on Darwin 8?
Date: Thu, 04 Aug 2005 03:50:00 -0000 [thread overview]
Message-ID: <20050804034851.GB18262@redhat.com> (raw)
In-Reply-To: <20050804013913.DE1101DC06D@bromo.msbb.uc.edu>
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.
The only way to bootstrap with -fstack-protector without
existing support in libc is to use a top-level bootstrap.
That said, I don't think this really addresses what you
want to accomplish...
> I am interested in doing this so that I can have a
> libgfortran built with -fstack-protector to try to track down
> a potential stack corruption problem. Thanks in advance for any
> advice.
This should be as simple as
make all-gcc
make all-target-libssp
make CFLAGS_FOR_TARGET='-O -g -fstack-protector-all' all-target-libgfortran
and then explicitly build your test program with -fstack-protector-all
so that the right libraries get linked in.
r~
next prev parent reply other threads:[~2005-08-04 3:50 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 [this message]
2005-08-08 22:48 ` Nix
-- 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=20050804034851.GB18262@redhat.com \
--to=rth@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=howarth@bromo.msbb.uc.edu \
/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).