Kevin Enderby 45aed251cc The integrated darwin assembler can hang in an infinite loop (or get an assert ... with a debug build) with this buggy .indirect_symbol directive usage: % cat test.s x: .indirect_symbol _y The assertion is because it is trying to get the symbol index for the symbol _y when it is writing out the indirect symbol table. This line of code in MachObjectWriter::WriteObject() : Write32(Asm.getSymbolData(*it->Symbol).getIndex()); And while there is a symbol _y it does not have any getSymbolData set which is only done in MachObjectWriter::BindIndirectSymbols() for pointer sections or stub sections. I added a check and an error in there to catch this in case something slips through. But to get a better error the parser should detect when a .indirect_symbol directive is used and it is not in a pointer section or stub section. To make that work I moved the handling of the indirect symbol out of the target independent AsmParser code into the DarwinAsmParser code that can check for the proper Mach-O section types. rdar://14825505 llvm-svn: 189497		2013-08-28 17:50:59 +00:00
..
AsmLexer.cpp	Support C99 hexadecimal floating-point literals in assembly	2013-08-14 14:23:31 +00:00
AsmParser.cpp	The integrated darwin assembler can hang in an infinite loop (or get an assert	2013-08-28 17:50:59 +00:00
CMakeLists.txt
COFFAsmParser.cpp	MC: Implement COFF .linkonce directive	2013-07-06 12:13:10 +00:00
DarwinAsmParser.cpp	The integrated darwin assembler can hang in an infinite loop (or get an assert	2013-08-28 17:50:59 +00:00
ELFAsmParser.cpp
LLVMBuild.txt
Makefile
MCAsmLexer.cpp
MCAsmParser.cpp
MCAsmParserExtension.cpp
MCTargetAsmParser.cpp