Displaying 5 results from an estimated 5 matches for "r_nearbyintl".
Did you mean:
nearbyintl
2019 Dec 17
2
Build failure on powerpc64
...long double as a valid case in a switch statement checking size
> * handling long double as a valid case in a switch statement checking size
> * memcpy from the address of a long double
> In format.c, we have (in order):
> * conditionally creating private_nearbyintl for R_nearbyintl
> * defining a static const long double tbl[]
> * use exact scaling factor in long double precision
> For most of these, it seems safe to leave them as is for ppc64. I would
> have thought that the gcc compiler might have had issue with:
> connections.c:
>...
2020 Mar 25
1
Build failure on powerpc64
...d case in a switch statement checking size
>>> * handling long double as a valid case in a switch statement checking size
>>> * memcpy from the address of a long double
>
>>> In format.c, we have (in order):
>>> * conditionally creating private_nearbyintl for R_nearbyintl
>>> * defining a static const long double tbl[]
>>> * use exact scaling factor in long double precision
>
>>> For most of these, it seems safe to leave them as is for ppc64. I would
>>> have thought that the gcc compiler might have had issue with:
>
>&...
2019 Dec 13
3
Build failure on powerpc64
>>>>> Tom Callaway
>>>>> on Thu, 12 Dec 2019 14:21:10 -0500 writes:
> Hi R folks,
> Went to build R 3.6.2 for Fedora/EPEL and got failures across the board.
> Disabling the test suite for all non-intel architectures resolves most of
> the failures, but powerpc64 dies in the compiler, specifically here:
> gcc -m64
2020 Mar 25
0
Build failure on powerpc64
...valid case in a switch statement checking size
>> * handling long double as a valid case in a switch statement checking size
>> * memcpy from the address of a long double
>> In format.c, we have (in order):
>> * conditionally creating private_nearbyintl for R_nearbyintl
>> * defining a static const long double tbl[]
>> * use exact scaling factor in long double precision
>> For most of these, it seems safe to leave them as is for ppc64. I would
>> have thought that the gcc compiler might have had issue with:
>> co...
2019 Dec 13
0
Build failure on powerpc64
...e u union define
* handling long double as a valid case in a switch statement checking size
* handling long double as a valid case in a switch statement checking size
* memcpy from the address of a long double
In format.c, we have (in order):
* conditionally creating private_nearbyintl for R_nearbyintl
* defining a static const long double tbl[]
* use exact scaling factor in long double precision
For most of these, it seems safe to leave them as is for ppc64. I would
have thought that the gcc compiler might have had issue with:
connections.c:
static long double ld1;...