From: Andrew Haley <aph@redhat.com>
To: David Daney <ddaney@avtrex.com>
Cc: Alexandre Oliva <aoliva@redhat.com>,
green@redhat.com, Hans Boehm <Hans.Boehm@hp.com>,
gcc-patches@gcc.gnu.org, java-patches@gcc.gnu.org
Subject: Re: Get libffi closures to cope with SELinux execmem/execmod
Date: Wed, 24 Jan 2007 17:09:00 -0000 [thread overview]
Message-ID: <17847.37555.38808.287238@zebedee.pink> (raw)
In-Reply-To: <45B79055.60503@avtrex.com>
David Daney writes:
> Well I'm not Anthony, but I am concerned about the overhead for
> systems that have an executable stack. I am thinking small
> embedded systems. It would be nice to have some sort of configure
> option that would allow us to build it the old way, or close to the
> old way if desired. That said, I have not measured the size of the
> dlmalloc and other additions to know if it really makes a
> difference. I am trying to put an entire Linux/GNU system with an
> application statically linked to libgcj into a 16MB flash memory.
> Adding more code to libgcj does not make it any easier.
Thanks for that. I agree; it makes no sense to burden non-SELinux
systems with all this stuff.
Andrew.
next prev parent reply other threads:[~2007-01-24 17:09 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 7:14 Alexandre Oliva
2007-01-18 7:28 ` Alexandre Oliva
2007-01-18 12:30 ` Andrew Haley
2007-01-18 12:47 ` Andrew Haley
2007-01-19 3:57 ` Alexandre Oliva
[not found] ` <Pine.GHP.4.58.0701190016420.29118@tomil.hpl.hp.com>
2007-01-22 21:28 ` Alexandre Oliva
2007-01-24 6:46 ` Alexandre Oliva
2007-01-24 15:47 ` Andrew Haley
2007-01-24 16:59 ` David Daney
2007-01-24 17:09 ` Andrew Haley [this message]
2007-01-25 5:59 ` Alexandre Oliva
2007-01-25 10:13 ` Andrew Haley
2007-01-25 17:21 ` David Daney
2007-01-25 17:32 ` Andrew Haley
2007-01-26 7:14 ` Alexandre Oliva
2007-01-26 7:28 ` Andrew Pinski
2007-01-24 17:33 ` Anthony Green
2007-01-25 21:52 ` Boehm, Hans
2007-01-26 8:11 ` Alexandre Oliva
2007-01-26 21:13 ` Boehm, Hans
2007-01-27 7:27 ` Alexandre Oliva
2007-01-31 23:43 ` Boehm, Hans
2007-02-05 14:21 ` Alexandre Oliva
2007-02-08 19:39 ` Andrew Haley
2007-02-08 20:46 ` Alexandre Oliva
2007-02-09 6:35 ` Hans Boehm
2007-02-09 18:27 ` Alexandre Oliva
2007-02-15 5:42 ` Hans Boehm
2007-02-15 7:24 ` Alexandre Oliva
2007-01-26 10:16 ` Andrew Haley
2007-02-15 7:14 ` Tom Tromey
2007-02-15 7:11 ` Tom Tromey
2007-02-18 23:09 ` Alexandre Oliva
2007-03-05 13:15 ` Tom Tromey
2007-03-07 7:29 ` Alexandre Oliva
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=17847.37555.38808.287238@zebedee.pink \
--to=aph@redhat.com \
--cc=Hans.Boehm@hp.com \
--cc=aoliva@redhat.com \
--cc=ddaney@avtrex.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=green@redhat.com \
--cc=java-patches@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).