[PATCH] D56335: [LLD] [docs] Add a known limitation to the comment about lld supporting GCC/MinGW object files. NFC.

[Martin Storsjö via Phabricator via llvm-commits]

mstorsjo created this revision.
mstorsjo added reviewers: ruiu, rnk.
Herald added subscribers: JDevlieghere, aprantl.

It's a rather long-winded comment, but we still want to announce that we mostly work out of the box with existing sysroots, just not ones with dwarf exceptions.

For libunwind with dwarf exceptions, a GCC style crtend.o with a terminator isn't needed, so it doesn't matter in such setups. For existing GCC setups, i686 either uses dwarf or SjLj (both are pretty much equally common I think), while the x86_64 ones either use SEH or SjLj.


Repository:
  rLLD LLVM Linker

https://reviews.llvm.org/D56335

Files:
  docs/ReleaseNotes.rst


Index: docs/ReleaseNotes.rst
===================================================================
--- docs/ReleaseNotes.rst
+++ docs/ReleaseNotes.rst
@@ -59,7 +59,10 @@
 * lld can now use existing normal MinGW sysroots with import libraries and
   CRT startup object files for GNU binutils. lld can handle most object
   files produced by GCC, and thus works as a drop-in replacement for
-  ld.bfd in such environments.
+  ld.bfd in such environments. (There are known issues with linking crtend.o
+  from GCC in setups with dwarf exceptions though, where object files are
+  linked in a different order than with GNU ld, inserting a dwarf exception
+  table terminator too early.)
 
 MachO Improvements
 ------------------


-------------- next part --------------
A non-text attachment was scrubbed...
Name: D56335.180326.patch
Type: text/x-patch
Size: 723 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20190104/36595506/attachment.bin>