Gecko [ sachasauda.akalacademy.ac.in ]

Name	Size	Permission
ANNOUNCE	3.68 KB	-rw-r--r--
AUTHORS	602 B	-rw-r--r--
COPYING	26.24 KB	-rw-r--r--
ChangeLog	102.46 KB	-rw-r--r--
HISTORY	3.76 KB	-rw-r--r--
NEWS	3.88 KB	-rw-r--r--
PORTING	19.02 KB	-rw-r--r--
README	3.96 KB	-rw-r--r--
SUPPORT	2.32 KB	-rw-r--r--
TESTS	6.09 KB	-rw-r--r--
THANKS	6.33 KB	-rw-r--r--
USERS	1.49 KB	-rw-r--r--

Code Editor : PORTING

____  _   _
  |  _ \| |_| |__                  ``A good magician never reveals
  | |_) | __| '_ \                   his secret; the unbelievable trick
  |  __/| |_| | | |                  becomes simple and obvious once it is
  |_|    \__|_| |_|                  explained. So too with UNIX.''

GNU Pth - The GNU Portable Threads

PORTING
  =======

SUCCESSFULLY TESTED PLATFORMS

The Pth package was successfully tested on the following platforms
  (and should automatically adjust to other platforms, of course):

HINTS FOR PORTING TO NEW PLATFORMS

In case you're not able to use Pth on a new and esoteric platform,
  here are a few hints.

Pth has only one part which perhaps has to be ported to new platforms: the
  machine context initialization, i.e. the function pth_mctx_set() in
  pth_mctx.c.  The exercise is to write a pth_mctx_set() function which
  initializes a `jmp_buf' (see setjmp(3)) with a given function and stack, so
  when the next longjmp(3) is done on this `jmp_buf', the function starts
  executing on the given stack.

By default, Pth uses a very tricky sigstack/sigaltstack() based approach for
  establishing this `jmp_buf' which is mostly portable to all major Unix
  platforms which support the involved POSIX functions (see rse-pmt.ps for a
  detailed description of the trick). So the chance is very high that this
  approach also works for forthcoming platforms and no real porting is
  required.

When this approach should not work (for instance brain-dead achient
  GNU/Linux versions have a dummy sigstack/sigaltstack(), so we've no chance
  this way), then you've to provide an alternative implementation. This
  usually is done be fiddling around with the ingredients of a `jmp_buf'
  structure. For this look inside your /usr/include/setjmp.h (plus files it
  includes) and there especially for things like _pc or JB_PC (the program
  counter) and _sp or JB_SP (the stack pointer). Then write an alternative
  pth_mctx_set() function in pth_mctx.c.

Currently, as mentioned, Pth requires such an alternative only under
  GNU/Linux where sigstack/sigaltstack() are dummy functions. Look at the
  GNU/Linux pth_mctx_set() variant in pth_mctx.c to get an impression what
  type of `jmp_buf' fiddling you perhaps have to do for esoteric platforms.
  Don't be confused by the fact that such specialized pth_mctx_set() functions
  are just a few lines long while the standard function is very large. That's
  all just needed for maximum portability.  The goal nevertheless only is to
  initialize a `jmp_buf' with PC and SP. That's all...

Additionally see the INSTALL document for the --enable-mctx-XXX options.
  These can be used to easily try out mctx combinations on a platform, too.

${this.title}

Code Editor : PORTING