|Bug Description||Versions present|
If a procedure argument is of a derived type with allocatable components, and the argument is intent(out) and
optional, then calling the procedure with this argument absent produces a segmentation fault.
XLF considers size-zero variables to be initially undefined, and disallows returning them as function results unless they
IBM reports that they
will fix this.
A where statement is vectorized by executing both branches and merging the result according to the mask. Therefore,
you cannot rely on the mask to filter out operations that result in out-of-bounds accesses, uses of uninitialized data, or
floating point exceptions.
Intel seems to
consider this a
limitation of their
May be fixed in 15?
If a routine uses an intrinsic function, and then is renamed (via use association) to have the same name as that
intrinsic, there's an internal error.
Reported via CISL
and again via forum.
Intel reports that a fix
will be available
"later this year" in
(2019-01-03) Given this vague statement, I'm not moving
this to the archive list yet.
array that has a dimension of size 0, to a routine that accepts it as an explicit-shape dummy argument.
(Regression from 13)
Reported to Intel via
account. Is fixed in Intel 17 (which will be released later this year)
|PGI||With FMA instructions enabled, runs on bluewaters do not give reproducible answers.|
Reported to PGI, but
no reduced case so