summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMartin Storsjo <martin@martin.st>2019-01-05 10:44:03 +0000
committerMartin Storsjo <martin@martin.st>2019-01-05 10:44:03 +0000
commit17fb13bb40cc9e5a3b0a51acfcfb73a58e691153 (patch)
treec90ed829b116ba4cb2036d5aadfef40d9942c004
parent5abe10ac210893178a17d3863707340f2cadbb30 (diff)
downloadbcm5719-llvm-17fb13bb40cc9e5a3b0a51acfcfb73a58e691153.tar.gz
bcm5719-llvm-17fb13bb40cc9e5a3b0a51acfcfb73a58e691153.zip
[docs] Add a known limitation to the comment about lld supporting GCC/MinGW object files. NFC.
Differential Revision: https://reviews.llvm.org/D56335 llvm-svn: 350465
-rw-r--r--lld/docs/ReleaseNotes.rst5
1 files changed, 4 insertions, 1 deletions
diff --git a/lld/docs/ReleaseNotes.rst b/lld/docs/ReleaseNotes.rst
index 30c1804374c..ee2286d1b22 100644
--- a/lld/docs/ReleaseNotes.rst
+++ b/lld/docs/ReleaseNotes.rst
@@ -59,7 +59,10 @@ MinGW Improvements
* 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
------------------
OpenPOWER on IntegriCloud