Since I have not seen any error like this from gcc, pgi, pathcc, xlc,
icc, open64 or suncc, I am pretty sure the problem is Clang-specific
even if not a true "bug" in Clang.
I just test everything I can get my hands on and report what I find.
If there is not a simple fix for this then it is not a big deal YET.
However, it is widely expected that Apple will move to a Clang-only (no
gcc/g++) release of Xcode as soon as they are able.
So, it *might* become a concern in the near future.
So, how should we proceed on this?
On 2/15/2012 8:38 AM, Dmitri Gribenko wrote:
> I don't know if it is a Clang bug, but here's my understanding of the problem.
[...excellent description removed...]
> I'm not sure if this is a bug in Clang because I don't know if Clang
> should have tried to instantiate create().
Paul H. Hargrove PHHargrove_at_[hidden]
Future Technologies Group
HPC Research Department Tel: +1-510-495-2352
Lawrence Berkeley National Laboratory Fax: +1-510-486-6900