On 16/11/15 13:42, Bernd Schmidt wrote:
On 11/13/2015 11:30 PM, Marc Glisse wrote:
+__asm__("posix_memalign");
Can't say I like the __asm__ after the #if/#else/#endif block.
It might also cause trouble if some systems like to prepend an
underscore, maybe?
Yeah, that's one of the things I h
On 11/13/2015 11:30 PM, Marc Glisse wrote:
+__asm__("posix_memalign");
Can't say I like the __asm__ after the #if/#else/#endif block.
It might also cause trouble if some systems like to prepend an
underscore, maybe?
Yeah, that's one of the things I had in mind when I suggested moving
this
On Fri, 13 Nov 2015, Bernd Schmidt wrote:
On 11/13/2015 06:11 PM, Szabolcs Nagy wrote:
Followup to https://gcc.gnu.org/ml/gcc-patches/2015-05/msg01433.html
The posix_memalign declaration is incompatible with musl libc in C++,
because of the exception specification (matters with -std=c++11
-ped
On Fri, Nov 13, 2015 at 09:58:30PM +0100, Bernd Schmidt wrote:
> On 11/13/2015 06:11 PM, Szabolcs Nagy wrote:
> >Followup to https://gcc.gnu.org/ml/gcc-patches/2015-05/msg01433.html
> >
> >The posix_memalign declaration is incompatible with musl libc in C++,
> >because of the exception specificatio
On 11/13/2015 06:11 PM, Szabolcs Nagy wrote:
Followup to https://gcc.gnu.org/ml/gcc-patches/2015-05/msg01433.html
The posix_memalign declaration is incompatible with musl libc in C++,
because of the exception specification (matters with -std=c++11
-pedantic-errors). It also pollutes the namespa
Followup to https://gcc.gnu.org/ml/gcc-patches/2015-05/msg01433.html
The posix_memalign declaration is incompatible with musl libc in C++,
because of the exception specification (matters with -std=c++11
-pedantic-errors). It also pollutes the namespace and lacks protection
against a potential ma
