|
77 | 77 | better interoperability with external source bases, a new example language
|
78 | 78 | front-end, and improvements in a few optimizations.</p>
|
79 | 79 |
|
80 |
| -<p>At this time, LLVM is known to correctly compile the C & C++ SPEC CPU2000 |
81 |
| -benchmarks with the C backend (X86 only), the Olden benchmarks, and the Ptrdist |
82 |
| -benchmarks. It has also been used to compile |
83 |
| -<b>many</b> other programs. LLVM now also works with a broad variety of |
84 |
| -C++ programs, though it has still received much less testing than the C |
85 |
| -front-end. |
| 80 | +<p>At this time, LLVM is known to correctly compile and run all non-unwinding C |
| 81 | +& C++ SPEC CPU2000 benchmarks, the Olden benchmarks, and the Ptrdist |
| 82 | +benchmarks. It has also been used to compile <b>many</b> other programs. LLVM |
| 83 | +now also works with a broad variety of C++ programs, though it has still |
| 84 | +received much less testing than the C front-end. |
86 | 85 | </p>
|
87 | 86 |
|
88 | 87 | <p>
|
89 |
| -Note that the Sparc and X86 backends do not currently support exception throwing |
90 |
| -or long jumping (including 253.perlbmk in SPEC). For these programs, you must |
91 |
| -use the C backend. Support for unwinding will be added in a future release. |
| 88 | +The LLVM native code generators are very stable, but do not currently support |
| 89 | +unwinding (exception throwing or <tt>longjmp</tt>ing), which prevent them from |
| 90 | +working with programs like the <tt>253.perlbmk</tt> in SPEC CPU2000. The C |
| 91 | +backend and the rest of LLVM does support these programs however, so you can |
| 92 | +still use LLVM with them. Support for unwinding will be added in a future |
| 93 | +release. |
92 | 94 | </p>
|
93 | 95 |
|
94 | 96 |
|
|
248 | 250 | <li><a href="http://llvm.cs.uiuc.edu/PR123">[X86] div and rem constant exprs invalidate iterators!</a></li>
|
249 | 251 | <li><a href="http://llvm.cs.uiuc.edu/PR130">[vmcore] Symbol table doesn't rename colliding variables during type resolution</a></li>
|
250 | 252 | <li><a href="http://llvm.cs.uiuc.edu/PR138">Archive reader does not understand 4.4BSD/Mac OS X long filenames</a></li>
|
| 253 | +<li><a href="http://llvm.cs.uiuc.edu/PR30">[llvm-ar] Command line arguments have funny syntax</a></li> |
251 | 254 | </ol>
|
252 | 255 |
|
253 | 256 |
|
|
320 | 323 |
|
321 | 324 | <p>This section contains all known problems with the LLVM system, listed by
|
322 | 325 | component. As new problems are discovered, they will be added to these
|
323 |
| -sections.</p> |
| 326 | +sections. If you run into a problem, please check the <a |
| 327 | +href="http://llvm.cs.uiuc.edu/bugs/">LLVM bug database</a>, and submit a bug if |
| 328 | +there isn't already one.</p> |
324 | 329 |
|
325 | 330 | </div>
|
326 | 331 |
|
|
666 | 671 | the "<tt>llvm/doc/</tt>" directory in the LLVM tree.</p>
|
667 | 672 |
|
668 | 673 | <p>If you have any questions or comments about LLVM, please feel free to contact
|
669 |
| -us via the mailing lists.</p> |
| 674 | +us via the <a href="http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev">mailing |
| 675 | +lists</a>.</p> |
670 | 676 |
|
671 | 677 | </div>
|
672 | 678 |
|
|
0 commit comments