From: Hollis Blanchard <hollis@penguinppc.org>
To: Albert Cahalan <acahalan@gmail.com>
Cc: linuxppc-dev@ozlabs.org,
debian-powerpc <debian-powerpc@lists.debian.org>,
Paul Mackerras <paulus@samba.org>
Subject: Re: PowerPC paxtest results w/ gcc-4.1
Date: Sun, 13 Aug 2006 11:45:01 -0500 [thread overview]
Message-ID: <1155487501.18244.0.camel@diesel> (raw)
In-Reply-To: <787b0d920608122111p79f29d74r600382658599cd63@mail.gmail.com>
On Sun, 2006-08-13 at 00:11 -0400, Albert Cahalan wrote:
>
> On 8/12/06, Paul Mackerras <paulus@samba.org> wrote:
> > Albert Cahalan writes:
> >
> > > VM_STACK_DEFAULT_FLAGS32 is wrong. A fail-safe
> > > default is important for security. If gcc on PowerPC ever
> > > does generate code which puts trampolines on the stack,
> > > then that can be fixed by converting to legal C code or
> > > by adding the fragile marking to the defective executables.
> > > Did gcc ever generate such code on PowerPC? If not,
> > > then there is no reason to ever allow an executable stack.
> >
> > I believe it did for nested procedures in C.
>
> I just disassembled libgcc. You're right. Eeeeeew.
> I filed a bug describing two better methods for this.
URL?
-Hollis
next prev parent reply other threads:[~2006-08-13 17:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-12 5:50 PowerPC paxtest results w/ gcc-4.1 Albert Cahalan
2006-08-12 11:35 ` Paul Mackerras
2006-08-12 14:36 ` Albert Cahalan
2006-08-12 23:54 ` Paul Mackerras
2006-08-13 2:48 ` Albert Cahalan
2006-08-13 3:23 ` Paul Mackerras
2006-08-13 4:11 ` Albert Cahalan
2006-08-13 16:45 ` Hollis Blanchard [this message]
2006-08-13 18:59 ` Albert Cahalan
2006-08-14 12:17 ` Matt Sealey
2006-08-14 14:20 ` Kumar Gala
2006-08-13 3:29 ` Alan Modra
2006-08-13 18:56 ` Albert Cahalan
2006-08-14 11:50 ` Matt Sealey
2006-08-15 3:59 ` Paul Mackerras
2006-08-16 10:59 ` Gabriel Paubert
2006-08-16 11:07 ` Paul Mackerras
2006-08-16 14:43 ` Albert Cahalan
2006-08-16 17:49 ` Segher Boessenkool
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=1155487501.18244.0.camel@diesel \
--to=hollis@penguinppc.org \
--cc=acahalan@gmail.com \
--cc=debian-powerpc@lists.debian.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.