From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jens Staal <staal1978@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Date: Mon,  7 Jan 2013 12:05:20 +0100
Message-ID: <1637616.FvtJCIHcLZ@krypton>
User-Agent: KMail/4.9.5 (Linux/3.7.1-2-ARCH; KDE/4.9.5; x86_64; ; )
In-Reply-To: <d9ae669115c31ca37f15264abd6b9d4e@kw.quanstro.net>
References: <1752877.EVzC7FFEmr@krypton>
	<d9ae669115c31ca37f15264abd6b9d4e@kw.quanstro.net>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"
Subject: Re: [9fans] a jmp_buf in APE question
Topicbox-Message-UUID: 02516598-ead8-11e9-9d60-3106f5b1d025

m=E5ndagen den 7 januari 2013 05.31.44 skrev  erik quanstrom:
> the structure within jmp_buf is entirely determined by the code in se=
tjmp.s
>=20
> i don't think it would be wise to rely on the structure of jmp_buf.

Do you mean by this that it would be unwise to do something like

"variable that needs to be =3D sp" =3D (jmp_buf) jb[0]
"variable that needs to be =3D pc" =3D (jmp_buf) jb[1]


this is how other similar ports of this package (GNU portable threads) =
have=20
been made, for example for win32

"variant 4", "variant 5" and "variant X" in the file pth_mctx.c are exa=
mples=20
of this strategy.*


*
for reference:
http://www.opensource.apple.com/source/ChatServer/ChatServer-37.1/jabbe=
rd-
src/jabberd/pth-1.4.0/pth_mctx.c?txt