All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: sparclinux@vger.kernel.org
Subject: PAGE_SIZE and native vs. emulated 32-bit SPARC ABI
Date: Thu, 30 Dec 2004 11:07:07 +0000	[thread overview]
Message-ID: <20041230110707.GC29332@holomorphy.com> (raw)

It seems that most/all 32-bit SPARC programs are written and compiled
for emulated 32-bit on sun4u, which has an 8KB PAGE_SIZE, and returns
8KB for getpagesize(). This is unfortunately causing spectacular
failures on some of my favorite regression tests for memory management,
which are interpreters using memory protection-based garbage collectors.

In particular, with a simple LD_PRELOAD to return a falsified 8KB
PAGE_SIZE, sbcl (a Common Lisp interpreter and compiler) may be made to
run, where it can't without such. The installation procedure runs the
interpreter, which is basically the extent of what I do with the ones
that run themselves during the installation procedure. For others just
starting up the interpreter serves as a simple testcase.

So, the question arises as to what to do about these ABI breakages.
It's unclear that changing the page size to 8192 unconditionally will
work, as there are suspected breakages in the other direction, as
another of those interpreters with protection-based GC that is strongly
suspected of being hardwired to a 4KB PAGE_SIZE.

Any ideas?


-- wli

             reply	other threads:[~2004-12-30 11:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-30 11:07 William Lee Irwin III [this message]
2004-12-30 11:50 ` PAGE_SIZE and native vs. emulated 32-bit SPARC ABI C.Newport
2004-12-30 12:13 ` William Lee Irwin III
2005-01-04 18:46 ` David S. Miller
2005-01-04 18:54 ` William Lee Irwin III

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=20041230110707.GC29332@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=sparclinux@vger.kernel.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.