Paul and all,
i just pushed
https://github.com/open-mpi/ompi/commit/b42e3441294e9fe787fe8e9ad7403d5b8e465163
when a buggy compiler is detected, configure now forces
OPAL_HAVE_CMPXCHG16B=0
this is enough to make opal_lifo test and make check happy again.
Cheers,
Gilles
On 2015/02/04 17:26, Gill
+1
great stuff
2015-02-04 5:55 GMT-07:00 Jeff Squyres (jsquyres) :
> OMPI devs --
>
> Per lots of previous discussions, you all know that you can't assign
> labels, milestones, or users to issues/pull requests on the ompi-release
> repo.
>
> Gilles has written a Github bot that will allow you to
OMPI devs --
Per lots of previous discussions, you all know that you can't assign labels,
milestones, or users to issues/pull requests on the ompi-release repo.
Gilles has written a Github bot that will allow you to do these things by
inserting special tokens in the text of issues/pull requests
Paul,
my previous email was misleading.
what i really meant is the opal_fifo test works fine with icc 2013u5
(the release before 2013sp1) and
icc 2013sp1u2 and later
so even if the reproducer fails with icc older that 2013sp1u2, that
might not impact ompi
since for other reasons, the bug is not
Giles,
Who says only 2 version are effected?
I have access to 9 revisions of icc.
Using your reduced case I find 7 that fail and only 2 (the latest two) that
pass.
Discounting icc-12 (which can't compile the test) that makes 6 versions
effected by the bug (not 2).
-Paul
$ for x in 12.1.5.339 13
Nathan,
imho, this is a compiler bug and only two versions are affected :
- intel icc 14.0.0.080 (aka 2013sp1)
- intel icc 14.0.1.106 (aka 2013sp1u1)
/* note the bug only occurs with -O1 and higher optimization levels */
here is attached a simple reproducer
a simple workaround is to configure wi
