Date: Mon, 13 Dec 2010 15:06:34 +0100 From: Tijl Coosemans <tijl@coosemans.org> To: Warner Losh <imp@bsdimp.com> Cc: Kostik Belousov <kostikbel@gmail.com>, mips@freebsd.org, Bruce Evans <brde@optusnet.com.au> Subject: Re: mips sig_atomic_t Message-ID: <201012131506.45650.tijl@coosemans.org> In-Reply-To: <4D05084C.10308@bsdimp.com> References: <201012121417.28343.tijl@coosemans.org> <4D05084C.10308@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart1379318.OyzAihz26h Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable On Sunday 12 December 2010 18:37:16 Warner Losh wrote: > On 12/12/2010 06:17, Tijl Coosemans wrote: >> In mips/include/signal.h sig_atomic_t is defined as int. Do you know if >> this can be 64 bit on the N64 ABI like on other 64 bit archs? How about >> N32? For reference, the POSIX definition of sig_atomic_t states: possibly >> volatile-qualified integer type of an object that can be accessed as an >> atomic entity, even in the presence of asynchronous interrupts. > LD and SD can be used to load/store an aligned 64-bit word in a=20 > mips64-like ISA. For mips32 ISAs, a 64-bit quantity is loaded/stored=20 > with two LW/SW instructions. >=20 > N64 and N32 can load/store these. However, N32 has an int set to=20 > 32-bits. I think this is OK. I'm still not sure if I understand the relations between the different acronyms correctly. Are these statements correct? There's a MIPS32 ISA and a MIPS64 ISA. The O32 ABI is ILP32 running on MIPS32. Like any ordinary 32 bit arch. The N64 ABI is LP64 running on MIPS64. Like any ordinary 64 bit arch. The N32 ABI is ILP32 running on MIPS64. It's pure MIPS64 not a compatibility mode or something like i386 code running on amd64. It has 64 bit registers and can do 64 bit load/store. --nextPart1379318.OyzAihz26h Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) iF4EABEIAAYFAk0GKHUACgkQfoCS2CCgtis7XgD7BflX8cMiDIPqXBLShd4qUXPL 37AedRnuCOzOLX+zDUUBAIBkd887aldXQGJgK3U7rfHwRuWMYLWPX9wmagC7VRPB =j36Y -----END PGP SIGNATURE----- --nextPart1379318.OyzAihz26h--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201012131506.45650.tijl>