Remove the hack that avoided mangling static functions in extern C contexts.

Weather we should give C language linkage to functions and variables with
internal linkage probably depends on how much code assumes it. The standard
says they should have no language linkage, but gcc and msvc assign them
C language linkage.

This commit removes the hack that was preventing the mangling on static
functions declare in extern C contexts. It is an experiment to see if we
can implement the rules in the standard.

If it turns out that many users depend on these functions and variables
having C language linkage, we should change isExternC instead and try
to convince the CWG to change the standard.

llvm-svn: 175937
This commit is contained in:
Rafael Espindola 2013-02-23 00:26:28 +00:00
parent 47f9f2d1e6
commit 16c8cf0e11
4 changed files with 9 additions and 24 deletions

View File

@ -385,15 +385,6 @@ bool ItaniumMangleContext::shouldMangleDeclName(const NamedDecl *D) {
// C functions are not mangled.
if (L == CLanguageLinkage)
return false;
// FIXME: Users assume they know the mangling of static functions
// declared in extern "C" contexts, so we cannot always mangle them.
// As an improvement, maybe we could mangle them only if they are actually
// overloaded.
const DeclContext *DC = FD->getDeclContext();
if (!DC->isRecord() &&
FD->getFirstDeclaration()->getDeclContext()->isExternCContext())
return false;
}
// Otherwise, no mangling is done outside C++ mode.

View File

@ -974,14 +974,6 @@ static bool canBeOverloaded(const FunctionDecl &D) {
if (D.isMain())
return false;
// FIXME: Users assume they know the mangling of static functions
// declared in extern "C" contexts. For now just disallow overloading these
// functions so that we can avoid mangling them.
const DeclContext *DC = D.getDeclContext();
if (!DC->isRecord() &&
D.getFirstDeclaration()->getDeclContext()->isExternCContext())
return false;
return true;
}

View File

@ -15,11 +15,13 @@ extern "C" {
extern "C" {
static void test2_f() {
}
// This is not required by the standard, but users assume they know
// the mangling of static functions in extern "C" contexts.
// CHECK: define internal void @test2_f(
// CHECK: define internal void @_Z7test2_fv
static void test2_f(int x) {
}
// CHECK: define internal void @_Z7test2_fi
void test2_use() {
test2_f();
test2_f(42);
}
}

View File

@ -12,12 +12,12 @@ namespace test1 {
}
}
// FIXME: This should be OK. Both test2_f don't have language linkage since they
// have internal linkage.
// This is OK. Both test2_f don't have language linkage since they have
// internal linkage.
extern "C" {
static void test2_f() { // expected-note {{previous definition is here}}
static void test2_f() {
}
static void test2_f(int x) { // expected-error {{conflicting types for 'test2_f'}}
static void test2_f(int x) {
}
}