Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 12 Dec 2010 10:37:16 -0700
From:      Warner Losh <imp@bsdimp.com>
To:        Tijl Coosemans <tijl@coosemans.org>
Cc:        Kostik Belousov <kostikbel@gmail.com>, mips@FreeBSD.org, Bruce Evans <brde@optusnet.com.au>
Subject:   Re: mips sig_atomic_t
Message-ID:  <4D05084C.10308@bsdimp.com>
In-Reply-To: <201012121417.28343.tijl@coosemans.org>
References:  <201012121417.28343.tijl@coosemans.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 12/12/2010 06:17, Tijl Coosemans wrote:
> Hi Warner,
>
> 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 
mips64-like ISA.  For mips32 ISAs, a 64-bit quantity is loaded/stored 
with two LW/SW instructions.

N64 and N32 can load/store these.  However, N32 has an int set to 
32-bits.  I think this is OK.

Warner




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D05084C.10308>