-
Bug
-
Resolution: Fixed
-
P3
-
12
-
b03
-
generic
-
solaris
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8215710 | 13 | Matthias Baesken | P3 | Resolved | Fixed | b02 |
| JDK-8222591 | 12u-cpu | Matthias Baesken | P3 | Resolved | Fixed | master |
| JDK-8221318 | 11.0.4 | Matthias Baesken | P4 | Resolved | Fixed | b01 |
Currently we disable C99 in the Solaris build by setting -xc99=%none%.
This differs from a lot of other build environments like gcc/Linux or VS2013/2017 on Windows where C99 features work.
We should remove this difference on Solaris and remove or replace the setting.
Kim Barrett mentioned :
"I merely mentioned the C++14 work as evidence that removing -xc99=%none% didn’t appear harmful."
However it will take more time until the C++14 change is in.
This differs from a lot of other build environments like gcc/Linux or VS2013/2017 on Windows where C99 features work.
We should remove this difference on Solaris and remove or replace the setting.
Kim Barrett mentioned :
"I merely mentioned the C++14 work as evidence that removing -xc99=%none% didn’t appear harmful."
However it will take more time until the C++14 change is in.
- backported by
-
-
- Resolved
-
-
JDK-8215710 do not disable c99 on Solaris
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
JDK-8224087 Compile C code for at least C99 Standard compliance
-
- Resolved
-