Re: [uclibc-ng-devel] [PATCH] bits/byteswap-common.h: import recent headers from glibc

2016-04-01 Thread Waldemar Brodkorb
Hi Anthony, Anthony G. Basile wrote, > From: "Anthony G. Basile" > > On systems where uClibc doesn't provide an arch specific byteswap.h, > we fall back on bits/byteswap-common.h. However, there is a bug > in this header in the __bswap_constant_64(x) macro. If, for

[PATCH] bits/byteswap-common.h: import recent headers from glibc

2016-03-25 Thread Anthony G. Basile
From: "Anthony G. Basile" On systems where uClibc doesn't provide an arch specific byteswap.h, we fall back on bits/byteswap-common.h. However, there is a bug in this header in the __bswap_constant_64(x) macro. If, for example, a double is passed, we get 'invalid operands

Re: [uclibc-ng-devel] [PATCH] bits/byteswap-common.h: import recent headers from glibc

2016-03-25 Thread Anthony G. Basile
On 3/25/16 6:35 AM, Waldemar Brodkorb wrote: > Hi Anthony, > Anthony G. Basile wrote, > >> From: "Anthony G. Basile" >> >> On systems where uClibc doesn't provide an arch specific byteswap.h, >> we fall back on bits/byteswap-common.h. However, there is a bug >> in this

[PATCH] bits/byteswap-common.h: import recent headers from glibc

2016-03-19 Thread Anthony G. Basile
From: "Anthony G. Basile" On systems where uClibc doesn't provide an arch specific byteswap.h, we fall back on bits/byteswap-common.h. However, there is a bug in this header in the __bswap_constant_64(x) macro. If, for example, a double is passed, we get "invalid operands