On Tue, 13 Oct 2015 13:41:29 +0200
Andrea Canciani wrote:
> On Tue, Oct 13, 2015 at 11:39 AM, Pekka Paalanen
> wrote:
>
> > On Tue, 13 Oct 2015 11:07:53 +0200
> > Andrea Canciani wrote:
> >
> > > On MacOS X an out-of-bounds access to an mmap-ed region typically
> > > results in a SIGBUS, but f
On MacOS X, according to the manpage of mprotect(), "When a program
violates the protections of a page, it gets a SIGBUS or SIGSEGV
signal.", but fence-image-self-test was only accepting a SIGSEGV as
notification of invalid access.
Fixes fence-image-self-test
Reviewed-by: Pekka Paalanen
---
tes
On Sun, 11 Oct 2015 20:59:41 -0700
Matt Turner wrote:
> We had lots of hacks to handle the inability to include xmmintrin.h
> without compiling with -msse (lest SSE instructions be used in
> pixman-mmx.c). Some recent version of gcc relaxed this restriction.
>
> Change configure.ac to test that
On Tue, 13 Oct 2015 11:07:53 +0200
Andrea Canciani wrote:
> On MacOS X an out-of-bounds access to an mmap-ed region typically
> results in a SIGBUS, but fence-image-self-test was only accepting a
> SIGSEGV as notification of invalid access.
Hi,
out-of-bounds may be true, but in this case we use
On MacOS X an out-of-bounds access to an mmap-ed region typically
results in a SIGBUS, but fence-image-self-test was only accepting a
SIGSEGV as notification of invalid access.
Fixes fence-image-self-test
---
test/fence-image-self-test.c | 12 +++-
test/utils.c | 6 +++---
On Sun, 11 Oct 2015 20:59:41 -0700
Matt Turner wrote:
> We had lots of hacks to handle the inability to include xmmintrin.h
> without compiling with -msse (lest SSE instructions be used in
> pixman-mmx.c). Some recent version of gcc relaxed this restriction.
>
> Change configure.ac to test that