aboutsummaryrefslogtreecommitdiff
path: root/llvm/docs/GettingStarted.html
diff options
context:
space:
mode:
authorAnton Korobeynikov <asl@math.spbu.ru>2009-05-04 10:24:46 +0000
committerAnton Korobeynikov <asl@math.spbu.ru>2009-05-04 10:24:46 +0000
commitdad5871f8448bac7216b54592e25e56ef38abe64 (patch)
tree07d216f497dfe615950ceb51317a9e81cdddfdc1 /llvm/docs/GettingStarted.html
parent6ebde279ae403ebd8692a7521a56c3c8de17c47a (diff)
downloadllvm-dad5871f8448bac7216b54592e25e56ef38abe64.zip
llvm-dad5871f8448bac7216b54592e25e56ef38abe64.tar.gz
llvm-dad5871f8448bac7216b54592e25e56ef38abe64.tar.bz2
It turns out that this version of gcc is broken (cygwin is well-known in shipping
of broken/buggy/snapshot-based compilers) llvm-svn: 70848
Diffstat (limited to 'llvm/docs/GettingStarted.html')
-rw-r--r--llvm/docs/GettingStarted.html3
1 files changed, 3 insertions, 0 deletions
diff --git a/llvm/docs/GettingStarted.html b/llvm/docs/GettingStarted.html
index 70c5912..1cca5ac 100644
--- a/llvm/docs/GettingStarted.html
+++ b/llvm/docs/GettingStarted.html
@@ -545,6 +545,9 @@ to miscompile parts of LLVM 2.4. One symptom is ValueSymbolTable complaining
about symbols remaining in the table on destruction.</p>
<p><b>GCC 4.1.2 20071124 (Red Hat 4.1.2-42)</b>: Suffers from the same symptoms
as the previous one. It appears to work with ENABLE_OPTIMIZED=0 (the default).</p>
+<p><b>Cygwin GCC 4.3.2 20080827 (beta) 2</b>:
+ Users <a href="http://llvm.org/PR4145">reported</a> various problems related
+ with link errors when using this GCC version.</p>
<p><b>GNU ld 2.16.X</b>. Some 2.16.X versions of the ld linker will produce very
long warning messages complaining that some ".gnu.linkonce.t.*" symbol was