linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Edelsohn <dje@watson.ibm.com>
To: Harald Welte <laforge@gnumonks.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: gcc/egcs stackguard on PPC ?
Date: Wed, 12 Dec 2001 00:29:09 -0500	[thread overview]
Message-ID: <200112120529.AAA29208@makai.watson.ibm.com> (raw)
In-Reply-To: Message from Harald Welte <laforge@gnumonks.org> of "Tue, 11 Dec 2001 08:44:27 +0100." <20011211084427.B23715@sunbeam.de.gnumonks.org>


>>>>> Harald Welte writes:

Harald> I was wondering if anybody has ever seen a working
gcc/egcs-stackguard on PPC.

	I believe the stack guard patch offered a few times by IBM Toyko
Research Lab was architecture-neutral and would have covered PowerPC
Linux.  However, the repeated offer was ignored by GCC developers.

David

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2001-12-12  5:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-11  7:44 gcc/egcs stackguard on PPC ? Harald Welte
2001-12-12  5:29 ` David Edelsohn [this message]

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=200112120529.AAA29208@makai.watson.ibm.com \
    --to=dje@watson.ibm.com \
    --cc=laforge@gnumonks.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /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 NNTP newsgroup(s).