summaryrefslogtreecommitdiffstats
path: root/llvm/lib/DebugInfo/Symbolize/SymbolizableObjectFile.cpp
diff options
context:
space:
mode:
authorMartin Storsjo <martin@martin.st>2018-05-09 09:21:53 +0000
committerMartin Storsjo <martin@martin.st>2018-05-09 09:21:53 +0000
commit284ab80f8d055bb350246c6e28d9a5579d784144 (patch)
treee239cdf69d0fedfc4842f6cfdf983bb213054252 /llvm/lib/DebugInfo/Symbolize/SymbolizableObjectFile.cpp
parentf1f8f4a1fd116323a6c4f3a4bde87243bab5668d (diff)
downloadbcm5719-llvm-284ab80f8d055bb350246c6e28d9a5579d784144.tar.gz
bcm5719-llvm-284ab80f8d055bb350246c6e28d9a5579d784144.zip
[COFF] Improve correctness of def parsing for GNU features
The operator == used for exporting a function with a different name in the DLL compared to the name in the import library (which is useful for adding linker level aliases for function in the import library) is a feature distinct and different from the operator = used for exporting a function with a different name (both in import library and DLL) than in the implementation producing the DLL. When creating an import library using dlltool, from a def file that contains forwards (Func = OtherDll.Func), this shouldn't affect the produced import library, which should still behave just as if it was a normal exported function. This clears a lot of confusion and subtle misunderstandings, and avoids a parameter that was used to avoid creating weak aliases when invoked from lld. (This parameter was added previously due to the existing conflation of the two features.) Differential Revision: https://reviews.llvm.org/D46245 llvm-svn: 331859
Diffstat (limited to 'llvm/lib/DebugInfo/Symbolize/SymbolizableObjectFile.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud