Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / external / llvm / ba2aa7859e7ae3b5276d902ed0edddbc5ec7355d / . / docs / ReleaseNotes-2.6.html
blob: 923d4e178cced01d0e4e1ce6da7a588af5bdc344 [file] [log] [blame]
Duncan Sandse2e4a892009-06-24 08:38:48 +0000[diff] [blame]1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
2 "http://www.w3.org/TR/html4/strict.dtd">
3<html>
4<head>
5 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
6 <link rel="stylesheet" href="llvm.css" type="text/css">
7 <title>LLVM 2.6 Release Notes</title>
8</head>
9<body>
10
11<div class="doc_title">LLVM 2.6 Release Notes</div>
12
13<ol>
14 <li><a href="#intro">Introduction</a></li>
15 <li><a href="#subproj">Sub-project Status Update</a></li>
16 <li><a href="#externalproj">External Projects Using LLVM 2.6</a></li>
17 <li><a href="#whatsnew">What's New in LLVM 2.6?</a></li>
18 <li><a href="GettingStarted.html">Installation Instructions</a></li>
19 <li><a href="#portability">Portability and Supported Platforms</a></li>
20 <li><a href="#knownproblems">Known Problems</a></li>
21 <li><a href="#additionalinfo">Additional Information</a></li>
22</ol>
23
24<div class="doc_author">
25 <p>Written by the <a href="http://llvm.org">LLVM Team</a></p>
26</div>
27
28<!-- *********************************************************************** -->
29<div class="doc_section">
30 <a name="intro">Introduction</a>
31</div>
32<!-- *********************************************************************** -->
33
34<div class="doc_text">
35
36<p>This document contains the release notes for the LLVM Compiler
37Infrastructure, release 2.6. Here we describe the status of LLVM, including
38major improvements from the previous release and significant known problems.
39All LLVM releases may be downloaded from the <a
40href="http://llvm.org/releases/">LLVM releases web site</a>.</p>
41
42<p>For more information about LLVM, including information about the latest
43release, please check out the <a href="http://llvm.org/">main LLVM
44web site</a>. If you have questions or comments, the <a
45href="http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev">LLVM Developer's Mailing
46List</a> is a good place to send them.</p>
47
48<p>Note that if you are reading this file from a Subversion checkout or the
49main LLVM web page, this document applies to the <i>next</i> release, not the
50current one. To see the release notes for a specific release, please see the
51<a href="http://llvm.org/releases/">releases page</a>.</p>
52
53</div>
54
55<!-- Unfinished features in 2.5:
56 Machine LICM
57 Machine Sinking
58 target-specific intrinsics
59 gold lto plugin
60 pre-alloc splitter, strong phi elim
61 <tt>llc -enable-value-prop</tt>, propagation of value info
62 (sign/zero ext info) from one MBB to another
63 debug info for optimized code
64 interpreter + libffi
65 postalloc scheduler: anti dependence breaking, hazard recognizer?
66
67initial support for debug line numbers when optimization enabled, not useful in
68 2.5 but will be for 2.6.
69
70 -->
71
72 <!-- for announcement email:
73 -->
74
75<!-- *********************************************************************** -->
76<div class="doc_section">
77 <a name="subproj">Sub-project Status Update</a>
78</div>
79<!-- *********************************************************************** -->
80
81<div class="doc_text">
82<p>
83The LLVM 2.6 distribution currently consists of code from the core LLVM
84repository &mdash;which roughly includes the LLVM optimizers, code generators
85and supporting tools &mdash; and the llvm-gcc repository. In addition to this
86code, the LLVM Project includes other sub-projects that are in development. The
87two which are the most actively developed are the <a href="#clang">Clang
88Project</a> and the <a href="#vmkit">VMKit Project</a>.
89</p>
90
91</div>
92
93
94<!--=========================================================================-->
95<div class="doc_subsection">
96<a name="clang">Clang: C/C++/Objective-C Frontend Toolkit</a>
97</div>
98
99<div class="doc_text">
100
101<p>The <a href="http://clang.llvm.org/">Clang project</a> is an effort to build
102a set of new 'LLVM native' front-end technologies for the LLVM optimizer and
103code generator. While Clang is not included in the LLVM 2.6 release, it is
104continuing to make major strides forward in all areas. Its C and Objective-C
105parsing and code generation support is now very solid. For example, it is
106capable of successfully building many real-world applications for X86-32
107and X86-64,
108including the <a href="http://wiki.freebsd.org/BuildingFreeBSDWithClang">FreeBSD
109kernel</a> and <a href="http://gcc.gnu.org/gcc-4.2/">gcc 4.2</a>. C++ is also
110making <a href="http://clang.llvm.org/cxx_status.html">incredible progress</a>,
111and work on templates has recently started. If you are
112interested in fast compiles and good diagnostics, we encourage you to try it out
113by <a href="http://clang.llvm.org/get_started.html">building from mainline</a>
114and reporting any issues you hit to the <a
115href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev">Clang front-end mailing
116list</a>.</p>
117
118<p>In the LLVM 2.6 time-frame, the Clang team has made many improvements:</p>
119
120<ul>
121<li>Something wonderful!</li>
122<li>Many many bugs are fixed and many features have been added.</li>
123</ul>
124</div>
125
126<!--=========================================================================-->
127<div class="doc_subsection">
128<a name="clangsa">Clang Static Analyzer</a>
129</div>
130
131<div class="doc_text">
132
133<p>Previously announced in the 2.4 LLVM release, the Clang project also
134includes an early stage static source code analysis tool for <a
135href="http://clang.llvm.org/StaticAnalysis.html">automatically finding bugs</a>
136in C and Objective-C programs. The tool performs a growing set of checks to find
137bugs that occur on a specific path within a program.</p>
138
139<p>In the LLVM 2.6 time-frame there have been many significant improvements to
140XYZ.</p>
141
142<p>The set of checks performed by the static analyzer continues to expand, and
143future plans for the tool include full source-level inter-procedural analysis
144and deeper checks such as buffer overrun detection. There are many opportunities
145to extend and enhance the static analyzer, and anyone interested in working on
146this project is encouraged to get involved!</p>
147
148</div>
149
150<!--=========================================================================-->
151<div class="doc_subsection">
152<a name="vmkit">VMKit: JVM/CLI Virtual Machine Implementation</a>
153</div>
154
155<div class="doc_text">
156<p>
157The <a href="http://vmkit.llvm.org/">VMKit project</a> is an implementation of
158a JVM and a CLI Virtual Machines (Microsoft .NET is an
159implementation of the CLI) using the Just-In-Time compiler of LLVM.</p>
160
161<p>Following LLVM 2.6, VMKit has its XYZ release that you can find on its
162<a href="http://vmkit.llvm.org/releases/">webpage</a>. The release includes
163bug fixes, cleanup and new features. The major changes are:</p>
164
165<ul>
166
167<li>Something wonderful!</li>
168
169</ul>
170</div>
171
172<!-- *********************************************************************** -->
173<div class="doc_section">
174 <a name="externalproj">External Projects Using LLVM 2.6</a>
175</div>
176<!-- *********************************************************************** -->
177
178<!--=========================================================================-->
179<div class="doc_subsection">
180<a name="pure">Pure</a>
181</div>
182
183<div class="doc_text">
184<p>
185<a href="http://pure-lang.googlecode.com/">Pure</a>
186is an algebraic/functional programming language based on term rewriting.
187Programs are collections of equations which are used to evaluate expressions in
188a symbolic fashion. Pure offers dynamic typing, eager and lazy evaluation,
189lexical closures, a hygienic macro system (also based on term rewriting),
190built-in list and matrix support (including list and matrix comprehensions) and
191an easy-to-use C interface. The interpreter uses LLVM as a backend to
192 JIT-compile Pure programs to fast native code.</p>
193
194<p>In addition to the usual algebraic data structures, Pure also has
195MATLAB-style matrices in order to support numeric computations and signal
196processing in an efficient way. Pure is mainly aimed at mathematical
197applications right now, but it has been designed as a general purpose language.
198The dynamic interpreter environment and the C interface make it possible to use
199it as a kind of functional scripting language for many application areas.
200</p>
201</div>
202
203
204<!--=========================================================================-->
205<div class="doc_subsection">
206<a name="ldc">LLVM D Compiler</a>
207</div>
208
209<div class="doc_text">
210<p>
211<a href="http://www.dsource.org/projects/ldc">LDC</a> is an implementation of
212the D Programming Language using the LLVM optimizer and code generator.
213The LDC project works great with the LLVM 2.6 release. General improvements in
214this
215cycle have included new inline asm constraint handling, better debug info
216support, general bugfixes, and better x86-64 support. This has allowed
217some major improvements in LDC, getting us much closer to being as
218fully featured as the original DMD compiler from DigitalMars.
219</p>
220</div>
221
222<!--=========================================================================-->
223<div class="doc_subsection">
224<a name="RoadsendPHP">Roadsend PHP</a>
225</div>
226
227<div class="doc_text">
228<p><a href="http://code.roadsend.com/rphp">Roadsend PHP</a> (rphp) is an open
229source implementation of the PHP programming
230language that uses LLVM for its optimizer, JIT, and static compiler. This is a
231reimplementation of an earlier project that is now based on LLVM.</p>
232</div>
233
Jeffrey Yasskinba2aa782009-06-24 21:09:13 +0000[diff] [blame^]234<!--=========================================================================-->
235<div class="doc_subsection">
236<a name="Unladen Swallow">Unladen Swallow</a>
237</div>
238
239<div class="doc_text">
240<p><a href="http://code.google.com/p/unladen-swallow/">Unladen Swallow</a> is a
241branch of <a href="http://python.org/">Python</a> intended to be fully
242compatible and significantly faster. It uses LLVM's optimization passes and JIT
243compiler.</p>
244</div>
245
Duncan Sandse2e4a892009-06-24 08:38:48 +0000[diff] [blame]246
247<!-- *********************************************************************** -->
248<div class="doc_section">
249 <a name="whatsnew">What's New in LLVM 2.6?</a>
250</div>
251<!-- *********************************************************************** -->
252
253<div class="doc_text">
254
255<p>This release includes a huge number of bug fixes, performance tweaks, and
256minor improvements. Some of the major improvements and new features are listed
257in this section.
258</p>
259</div>
260
261<!--=========================================================================-->
262<div class="doc_subsection">
263<a name="majorfeatures">Major New Features</a>
264</div>
265
266<div class="doc_text">
267
268<p>LLVM 2.6 includes several major new capabilities:</p>
269
270<ul>
271<li>Something wonderful!</li>
272</ul>
273
274</div>
275
276
277<!--=========================================================================-->
278<div class="doc_subsection">
279<a name="llvm-gcc">llvm-gcc 4.2 Improvements</a>
280</div>
281
282<div class="doc_text">
283
284<p>LLVM fully supports the llvm-gcc 4.2 front-end, which marries the GCC
285front-ends and driver with the LLVM optimizer and code generator. It currently
286includes support for the C, C++, Objective-C, Ada, and Fortran front-ends.</p>
287
288<ul>
289<li>Something wonderful!</li>
290</ul>
291
292</div>
293
294
295<!--=========================================================================-->
296<div class="doc_subsection">
297<a name="coreimprovements">LLVM IR and Core Improvements</a>
298</div>
299
300<div class="doc_text">
301<p>LLVM IR has several new features that are used by our existing front-ends and
302can be useful if you are writing a front-end for LLVM:</p>
303
304<ul>
305<li>Something wonderful!</li>
306</ul>
307
308</div>
309
310<!--=========================================================================-->
311<div class="doc_subsection">
312<a name="optimizer">Optimizer Improvements</a>
313</div>
314
315<div class="doc_text">
316
317<p>In addition to a large array of bug fixes and minor performance tweaks, this
318release includes a few major enhancements and additions to the optimizers:</p>
319
320<ul>
321
322<li>Something wonderful!</li>
323
324</ul>
325
326</div>
327
328<!--=========================================================================-->
329<div class="doc_subsection">
330<a name="codegen">Target Independent Code Generator Improvements</a>
331</div>
332
333<div class="doc_text">
334
335<p>We have put a significant amount of work into the code generator
336infrastructure, which allows us to implement more aggressive algorithms and make
337it run faster:</p>
338
339<ul>
340
341<li>Something wonderful!</li>
342</ul>
343</div>
344
345<!--=========================================================================-->
346<div class="doc_subsection">
347<a name="x86">X86-32 and X86-64 Target Improvements</a>
348</div>
349
350<div class="doc_text">
351<p>New features of the X86 target include:
352</p>
353
354<ul>
355
356<li>Something wonderful!</li>
357</ul>
358
359</div>
360
361<!--=========================================================================-->
362<div class="doc_subsection">
363<a name="pic16">PIC16 Target Improvements</a>
364</div>
365
366<div class="doc_text">
367<p>New features of the PIC16 target include:
368</p>
369
370<ul>
371<li>Something wonderful!</li>
372</ul>
373
374<p>Things not yet supported:</p>
375
376<ul>
377<li>Floating point.</li>
378<li>Passing/returning aggregate types to and from functions.</li>
379<li>Variable arguments.</li>
380<li>Indirect function calls.</li>
381<li>Interrupts/programs.</li>
382<li>Debug info.</li>
383</ul>
384
385</div>
386
387
388<!--=========================================================================-->
389<div class="doc_subsection">
390<a name="llvmc">Improvements in LLVMC</a>
391</div>
392
393<div class="doc_text">
394<p>New features include:</p>
395
396<ul>
397<li>Something wonderful!</li>
398</ul>
399
400</div>
401
402
403<!--=========================================================================-->
404<div class="doc_subsection">
405<a name="changes">Major Changes and Removed Features</a>
406</div>
407
408<div class="doc_text">
409
410<p>If you're already an LLVM user or developer with out-of-tree changes based
411on LLVM 2.4, this section lists some "gotchas" that you may run into upgrading
412from the previous release.</p>
413
414<ul>
415
416<li>Something horrible!</li>
417
418</ul>
419
420
421<p>In addition, many APIs have changed in this release. Some of the major LLVM
422API changes are:</p>
423
424<ul>
425<li>The <tt>getABITypeSize</tt> methods are now called <tt>getAllocSize</tt>.</li>
426</ul>
427
428</div>
429
430
431
432<!-- *********************************************************************** -->
433<div class="doc_section">
434 <a name="portability">Portability and Supported Platforms</a>
435</div>
436<!-- *********************************************************************** -->
437
438<div class="doc_text">
439
440<p>LLVM is known to work on the following platforms:</p>
441
442<ul>
443<li>Intel and AMD machines (IA32, X86-64, AMD64, EMT-64) running Red Hat
444Linux, Fedora Core and FreeBSD (and probably other unix-like systems).</li>
445<li>PowerPC and X86-based Mac OS X systems, running 10.3 and above in 32-bit
446and 64-bit modes.</li>
447<li>Intel and AMD machines running on Win32 using MinGW libraries (native).</li>
448<li>Intel and AMD machines running on Win32 with the Cygwin libraries (limited
449 support is available for native builds with Visual C++).</li>
450<li>Sun UltraSPARC workstations running Solaris 10.</li>
451<li>Alpha-based machines running Debian GNU/Linux.</li>
452<li>Itanium-based (IA64) machines running Linux and HP-UX.</li>
453</ul>
454
455<p>The core LLVM infrastructure uses GNU autoconf to adapt itself
456to the machine and operating system on which it is built. However, minor
457porting may be required to get LLVM to work on new platforms. We welcome your
458portability patches and reports of successful builds or error messages.</p>
459
460</div>
461
462<!-- *********************************************************************** -->
463<div class="doc_section">
464 <a name="knownproblems">Known Problems</a>
465</div>
466<!-- *********************************************************************** -->
467
468<div class="doc_text">
469
470<p>This section contains significant known problems with the LLVM system,
471listed by component. If you run into a problem, please check the <a
472href="http://llvm.org/bugs/">LLVM bug database</a> and submit a bug if
473there isn't already one.</p>
474
475</div>
476
477<!-- ======================================================================= -->
478<div class="doc_subsection">
479 <a name="experimental">Experimental features included with this release</a>
480</div>
481
482<div class="doc_text">
483
484<p>The following components of this LLVM release are either untested, known to
485be broken or unreliable, or are in early development. These components should
486not be relied on, and bugs should not be filed against them, but they may be
487useful to some people. In particular, if you would like to work on one of these
488components, please contact us on the <a
489href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">LLVMdev list</a>.</p>
490
491<ul>
492<li>The MSIL, IA64, Alpha, SPU, MIPS, and PIC16 backends are experimental.</li>
493<li>The <tt>llc</tt> "<tt>-filetype=asm</tt>" (the default) is the only
494 supported value for this option.</li>
495</ul>
496
497</div>
498
499<!-- ======================================================================= -->
500<div class="doc_subsection">
501 <a name="x86-be">Known problems with the X86 back-end</a>
502</div>
503
504<div class="doc_text">
505
506<ul>
507 <li>The X86 backend does not yet support
508 all <a href="http://llvm.org/PR879">inline assembly that uses the X86
509 floating point stack</a>. It supports the 'f' and 't' constraints, but not
510 'u'.</li>
511 <li>The X86 backend generates inefficient floating point code when configured
512 to generate code for systems that don't have SSE2.</li>
513 <li>Win64 code generation wasn't widely tested. Everything should work, but we
514 expect small issues to happen. Also, llvm-gcc cannot build the mingw64
515 runtime currently due
516 to <a href="http://llvm.org/PR2255">several</a>
517 <a href="http://llvm.org/PR2257">bugs</a> and due to lack of support for
518 the
519 'u' inline assembly constraint and for X87 floating point inline assembly.</li>
520 <li>The X86-64 backend does not yet support the LLVM IR instruction
521 <tt>va_arg</tt>. Currently, the llvm-gcc and front-ends support variadic
522 argument constructs on X86-64 by lowering them manually.</li>
523</ul>
524
525</div>
526
527<!-- ======================================================================= -->
528<div class="doc_subsection">
529 <a name="ppc-be">Known problems with the PowerPC back-end</a>
530</div>
531
532<div class="doc_text">
533
534<ul>
535<li>The Linux PPC32/ABI support needs testing for the interpreter and static
536compilation, and lacks support for debug information.</li>
537</ul>
538
539</div>
540
541<!-- ======================================================================= -->
542<div class="doc_subsection">
543 <a name="arm-be">Known problems with the ARM back-end</a>
544</div>
545
546<div class="doc_text">
547
548<ul>
549<li>Thumb mode works only on ARMv6 or higher processors. On sub-ARMv6
550processors, thumb programs can crash or produce wrong
551results (<a href="http://llvm.org/PR1388">PR1388</a>).</li>
552<li>Compilation for ARM Linux OABI (old ABI) is supported but not fully tested.
553</li>
554<li>There is a bug in QEMU-ARM (&lt;= 0.9.0) which causes it to incorrectly
555 execute
556programs compiled with LLVM. Please use more recent versions of QEMU.</li>
557</ul>
558
559</div>
560
561<!-- ======================================================================= -->
562<div class="doc_subsection">
563 <a name="sparc-be">Known problems with the SPARC back-end</a>
564</div>
565
566<div class="doc_text">
567
568<ul>
569<li>The SPARC backend only supports the 32-bit SPARC ABI (-m32); it does not
570 support the 64-bit SPARC ABI (-m64).</li>
571</ul>
572
573</div>
574
575<!-- ======================================================================= -->
576<div class="doc_subsection">
577 <a name="mips-be">Known problems with the MIPS back-end</a>
578</div>
579
580<div class="doc_text">
581
582<ul>
583<li>The O32 ABI is not fully supported.</li>
584<li>64-bit MIPS targets are not supported yet.</li>
585</ul>
586
587</div>
588
589<!-- ======================================================================= -->
590<div class="doc_subsection">
591 <a name="alpha-be">Known problems with the Alpha back-end</a>
592</div>
593
594<div class="doc_text">
595
596<ul>
597
598<li>On 21164s, some rare FP arithmetic sequences which may trap do not have the
599appropriate nops inserted to ensure restartability.</li>
600
601</ul>
602</div>
603
604<!-- ======================================================================= -->
605<div class="doc_subsection">
606 <a name="ia64-be">Known problems with the IA64 back-end</a>
607</div>
608
609<div class="doc_text">
610
611<ul>
612<li>The Itanium backend is highly experimental and has a number of known
613 issues. We are looking for a maintainer for the Itanium backend. If you
614 are interested, please contact the LLVMdev mailing list.</li>
615</ul>
616
617</div>
618
619<!-- ======================================================================= -->
620<div class="doc_subsection">
621 <a name="c-be">Known problems with the C back-end</a>
622</div>
623
624<div class="doc_text">
625
626<ul>
627<li><a href="http://llvm.org/PR802">The C backend has only basic support for
628 inline assembly code</a>.</li>
629<li><a href="http://llvm.org/PR1658">The C backend violates the ABI of common
630 C++ programs</a>, preventing intermixing between C++ compiled by the CBE and
631 C++ code compiled with <tt>llc</tt> or native compilers.</li>
632<li>The C backend does not support all exception handling constructs.</li>
633<li>The C backend does not support arbitrary precision integers.</li>
634</ul>
635
636</div>
637
638
639<!-- ======================================================================= -->
640<div class="doc_subsection">
641 <a name="c-fe">Known problems with the llvm-gcc C front-end</a>
642</div>
643
644<div class="doc_text">
645
646<p>llvm-gcc does not currently support <a href="http://llvm.org/PR869">Link-Time
647Optimization</a> on most platforms "out-of-the-box". Please inquire on the
648LLVMdev mailing list if you are interested.</p>
649
650<p>The only major language feature of GCC not supported by llvm-gcc is
651 the <tt>__builtin_apply</tt> family of builtins. However, some extensions
652 are only supported on some targets. For example, trampolines are only
653 supported on some targets (these are used when you take the address of a
654 nested function).</p>
655
656<p>If you run into GCC extensions which are not supported, please let us know.
657</p>
658
659</div>
660
661<!-- ======================================================================= -->
662<div class="doc_subsection">
663 <a name="c++-fe">Known problems with the llvm-gcc C++ front-end</a>
664</div>
665
666<div class="doc_text">
667
668<p>The C++ front-end is considered to be fully
669tested and works for a number of non-trivial programs, including LLVM
670itself, Qt, Mozilla, etc.</p>
671
672<ul>
673<li>Exception handling works well on the X86 and PowerPC targets. Currently
674 only Linux and Darwin targets are supported (both 32 and 64 bit).</li>
675</ul>
676
677</div>
678
679<!-- ======================================================================= -->
680<div class="doc_subsection">
681 <a name="fortran-fe">Known problems with the llvm-gcc Fortran front-end</a>
682</div>
683
684<div class="doc_text">
685<ul>
686<li>Fortran support generally works, but there are still several unresolved bugs
687 in Bugzilla. Please see the tools/gfortran component for details.</li>
688</ul>
689</div>
690
691<!-- ======================================================================= -->
692<div class="doc_subsection">
693 <a name="ada-fe">Known problems with the llvm-gcc Ada front-end</a>
694</div>
695
696<div class="doc_text">
697The llvm-gcc 4.2 Ada compiler works fairly well; however, this is not a mature
698technology, and problems should be expected.
699<ul>
700<li>The Ada front-end currently only builds on X86-32. This is mainly due
701to lack of trampoline support (pointers to nested functions) on other platforms.
702However, it <a href="http://llvm.org/PR2006">also fails to build on X86-64</a>
703which does support trampolines.</li>
704<li>The Ada front-end <a href="http://llvm.org/PR2007">fails to bootstrap</a>.
705This is due to lack of LLVM support for <tt>setjmp</tt>/<tt>longjmp</tt> style
706exception handling, which is used internally by the compiler.
707Workaround: configure with --disable-bootstrap.</li>
708<li>The c380004, <a href="http://llvm.org/PR2010">c393010</a>
709and <a href="http://llvm.org/PR2421">cxg2021</a> ACATS tests fail
710(c380004 also fails with gcc-4.2 mainline).
711If the compiler is built with checks disabled then <a href="http://llvm.org/PR2010">c393010</a>
712causes the compiler to go into an infinite loop, using up all system memory.</li>
713<li>Some GCC specific Ada tests continue to crash the compiler.</li>
714<li>The -E binder option (exception backtraces)
715<a href="http://llvm.org/PR1982">does not work</a> and will result in programs
716crashing if an exception is raised. Workaround: do not use -E.</li>
717<li>Only discrete types <a href="http://llvm.org/PR1981">are allowed to start
718or finish at a non-byte offset</a> in a record. Workaround: do not pack records
719or use representation clauses that result in a field of a non-discrete type
720starting or finishing in the middle of a byte.</li>
721<li>The <tt>lli</tt> interpreter <a href="http://llvm.org/PR2009">considers
722'main' as generated by the Ada binder to be invalid</a>.
723Workaround: hand edit the file to use pointers for <tt>argv</tt> and
724<tt>envp</tt> rather than integers.</li>
725<li>The <tt>-fstack-check</tt> option <a href="http://llvm.org/PR2008">is
726ignored</a>.</li>
727</ul>
728</div>
729
730<!-- *********************************************************************** -->
731<div class="doc_section">
732 <a name="additionalinfo">Additional Information</a>
733</div>
734<!-- *********************************************************************** -->
735
736<div class="doc_text">
737
738<p>A wide variety of additional information is available on the <a
739href="http://llvm.org">LLVM web page</a>, in particular in the <a
740href="http://llvm.org/docs/">documentation</a> section. The web page also
741contains versions of the API documentation which is up-to-date with the
742Subversion version of the source code.
743You can access versions of these documents specific to this release by going
744into the "<tt>llvm/doc/</tt>" directory in the LLVM tree.</p>
745
746<p>If you have any questions or comments about LLVM, please feel free to contact
747us via the <a href="http://llvm.org/docs/#maillist"> mailing
748lists</a>.</p>
749
750</div>
751
752<!-- *********************************************************************** -->
753
754<hr>
755<address>
756 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
757 src="http://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid CSS"></a>
758 <a href="http://validator.w3.org/check/referer"><img
759 src="http://www.w3.org/Icons/valid-html401-blue" alt="Valid HTML 4.01"></a>
760
761 <a href="http://llvm.org/">LLVM Compiler Infrastructure</a><br>
762 Last modified: $Date$
763</address>
764
765</body>
766</html>