o they should just use my version as a basis and fork/simplify
it (even i maintain private forks of the public version).
as for the location of c-common.h, upstream gcc moved it under c-family in
2010 after the release of 4.5, so it should be where gcc-common.h expects
it and i'm not sure how i
On 9 Dec 2016 at 13:48, Andrew Donnellan wrote:
> >> as for the solutions, the general advice should enable the use of otherwise
> >> failing gcc versions instead of forcing updating to new ones (though the
> >> latter is advisable for other reasons but not everyone's in the position to
> >> do so
27;s part of the target tuple so in general arch maintainers should
test
the target tuples used on their arch with all the supported gcc versions
(speaking
of CC, not HOSTCC/HOSTCXX).
cheers,
PaX Team
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
On 9 Jul 2016 at 14:27, Andy Lutomirski wrote:
> On Jul 6, 2016 6:25 PM, "Kees Cook" wrote:
> >
> > Hi,
> >
> > This is a start of the mainline port of PAX_USERCOPY[1]. After I started
> > writing tests (now in lkdtm in -next) for Casey's earlier port[2], I
> > kept tweaking things further and fu
On 10 Jul 2016 at 11:16, Ingo Molnar wrote:
> * PaX Team wrote:
>
> > On 9 Jul 2016 at 14:27, Andy Lutomirski wrote:
> >
> > > I like the series, but I have one minor nit to pick. The effect of this
> > > series is to harden usercopy,
