[update LLVM+LLDB] Switch to the custom DW_LANG_Swift specifier.

Retire DW_TAG_restrict in favor of DW_TAG_APPLE_metatype.

<rdar://problem/16513629> Cleanup DWARF output for WWDC

Swift SVN r17949
This commit is contained in:
Adrian Prantl
2014-05-12 19:17:54 +00:00
parent 14a6697ba5
commit 932d08d89b
2 changed files with 25 additions and 41 deletions

View File

@@ -20,28 +20,6 @@
#include "llvm/Support/Dwarf.h"
namespace swift {
//===--- BEGIN "TO BE FIXED IN A SWIFT BRANCH OF LLVM" ---===//
//
// DWARF constants.
//
// The first unused language value in DWARF v5 is DW_LANG_Rust+1 =
// 0x1d. We can't use it, because LLVM asserts that there are no
// languages >DW_LANG_Python=0x14. Wouldn't it would be much more
// appropriate to use a constant in DW_LANG_lo_user..DW_LANG_hi_user
// anyway, you may ask? Well, CompileUnit::constructTypeDIE() will
// always use a DW_FORM_data1, which is too small for that range! And
// by fixing that in LLVM we would hint at developing a new language.
// So instead, let's hijack a language with a very low potential for
// accidental conflicts for now.
//
typedef enum {
DW_LANG_Swift = 0xf,
DW_LANG_ObjC = llvm::dwarf::DW_LANG_ObjC, // For symmetry.
} dwarf;
//
//===--------- END "TO BE FIXED IN A SWIFT BRANCH OF LLVM" --------===//
static const char MachOASTSegmentName[] = "__SWIFT";
static const char MachOASTSectionName[] = "__ast";
}