Displaying 3 results from an estimated 3 matches for "pluginfile1".
Did you mean:
pluginfile2
2010 Aug 05
4
[LLVMdev] LLVMC tests failing when building with clang
Hi,
After building llvm with clang the llvmc tests are failing with:
llvmc: Node llc is not in graph
Anyone else see this ? (TOT llvm & clang)
-Argiris
2010 Aug 13
0
[LLVMdev] LLVMC tests failing when building with clang
...to a bug in clang:
// file1.cpp
namespace {
class Plugin {
};
}
// file2.cpp
namespace {
class Plugin {
};
}
Clang can't distinguish between file1::Plugin and
file2::Plugin. Is this a known issue? I've added a workaround for
now: change the names of file1::Plugin and file2::Plugin to
Pluginfile1 and Pluginfile2, respectively.
2010 Aug 13
1
[LLVMdev] LLVMC tests failing when building with clang
...}
>
> // file2.cpp
>
> namespace {
>
> class Plugin {
> };
> }
>
> Clang can't distinguish between file1::Plugin and
> file2::Plugin. Is this a known issue? I've added a workaround for
> now: change the names of file1::Plugin and file2::Plugin to
> Pluginfile1 and Pluginfile2, respectively.
Aha! Good catch. It turns out that Clang gives non-internal linkage to member
functions of member class templates instantiated at members of anonymous
namespaces. Fixed in r111012.
John.