ISSUES of glibc 2.26 (GNU C LIBRARY) with CUDA and ICC
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
glibc (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
I reported that glibc 2.26-0ubuntu1 ( adopted in Artful-proposed on Sep 5.) causes compilation error by using NVIDIA's CUDA9.0 or Intel's ICC
Under glibc 2.24, they work.
It maybe comes from glibc226's new feature, i.e. "128-bit floating point as defined by ISO/IEC/IEEE 60559:2011 (IEEE 754-2008) and ISO/IEC TS 18661-3:2015" . (see below, pls)
So, if possible, would like to withdraw from adopting glibc2.26 (and switch back to glibc2.24 or glibc 2.25)?
evidence
----------
1. Here is part of message during compiing Tensorflow with CUDA on UBUNTU17.10 beta with proposed-
--------------
typedef _Complex float __cfloat128 __attribute__ ((__mode__ (__TC__)));
INFO: From Compiling external/
/usr/include/
/usr/include/
--------------
2. Forums in Intel and NVIDIA
where issues the problems around glibc.2.26
Intel
https:/
NVIDIA
https:/
description: | updated |
summary: |
- ISSUES of GLIBC2.26 + ISSUES of GLIBC 2.26 (GNU C LIBRARY) with CUDA and ICC |
summary: |
- ISSUES of GLIBC 2.26 (GNU C LIBRARY) with CUDA and ICC + ISSUES of glibc 2.26 (GNU C LIBRARY) with CUDA and ICC |
tags: | added: artful artful-proposed |
> So, if possible, would like to withdraw from adopting glibc2.26
> (and switch back to glibc2.24 or glibc 2.25)?
no.