| blob | 2c893a9087a28eb8db9c7e2e2dc3402111fdbbd7 |
2 <html>
3 <head>
6 </head>
7 <body>
9 </h2>
12 <ul>
14 </li>
16 </li>
18 </li>
23 </ul>
25 Similar versions of the above systems should work and other Unix
26 platforms may
27 work.
28 Although the compiler will
29 probably work on most architectures, the D
30 runtime library will still need to be updated to support them.<br>
37 The MacOS X universal binary package requires XCode 2.4.1 or the
38 equivalent version of cctools.
44 <ul>
50 package</a></li>
60 </ul>
70 <ul>
76 Compiler for GCC</a><br>
81 </li>
87 Programming Language</a></li>
93 Links Page</a><br>
98 </li>
104 D.gnu newsgroup</a></li>
109 <li>For general D discussion, the <a href="news://news.digitalmars.com/digitalmars.D">digitalmars.D</a>
111 newsgroups<br>
116 </li>
122 Collection</a></li>
128 OS X binary
129 distribution</a><br>
134 </li>
139 </ul>
149 David Friedman<br>
164 </h3>
174 <ul>
180 page for known failing cases.<br>
185 </li>
190 <li>Debugging information may have a few problems. To enable D
191 name
197 </li>
202 <li>Some targets do not support once-only linking. A workaround
203 is to
204 manually control template emission. See the <span style="font-family: monospace;">-femit-templates</span>
205 option below. For Darwin, Apple's GCC 3.x compiler supports
206 one-only linking, but GDC does not build with those sources. There are
207 no
213 </li>
221 <ol>
229 </ol>
234 <li>Complex floating point operations may not work the same as
235 DMD.</li>
240 <li>Some math functions behave differently due to different
241 implementations of the extended floating-point type.</li>
251 <li>Because of <a href="http://groups-beta.google.com/groups?hl=en&q=%22large+executables+on+AIX%22&qt_s=Search">a
252 problem on AIX</a>, the linker will pull in more modules than
253 needed.<br>
258 </li>
263 <li>Some C libraries (Cygwin, MinGW, AIX) don't handle
264 floating-point
265 formatting and parsing in a standard way.<br>
270 </li>
275 </ul>
285 <ul>
291 in variadic functions is the target-specific <span style="font-family: monospace;">va_list</span>
292 type. The only
293 portable way
296 template. In particular, you cannot construct a <span style="font-family: monospace;">va_list</span> from a
297 pointer to data
298 an expect it to work.<br>
303 </li>
308 <li>In assembler code, direct access to parameters in naked
309 functions
310 works differently. Frame relative addressing through <span style="font-family: monospace;">[ESP+4]</span> does
311 work the same way.<br>
316 </li>
321 <li>Currently, GDC uses the C calling convention for all
322 functions
329 <li>GDC allows <span style="font-family: monospace;">catch</span> statements in <span style="font-family: monospace;">finally</span>
330 blocks.</li>
336 is not
337 supported.</li>
342 <li>Some targets do not have a distinct extended floating-point
345 are the same
346 size.</li>
351 <li>On Win32, GDC allocates 12 bytes for the <span style="font-family: monospace;">real</span> type,
352 while DMD allocates
353 10 bytes. This also applies to the components of the <span style="font-family: monospace;">creal</span> type.<br>
358 </li>
363 </ul>
373 <ul>
379 difficult.
380 It is recommended that you use only assembler statements in a naked
381 function. When generating position-independent code, accessing global symbols in a naked function will result in an error.</li>
386 <li>Jumps from assembler statements will not run cleanups (auto
387 and
388 finally)</li>
393 </ul>
408 The compiler driver is named 'gdc' and accepts the standard GCC
409 options. There is also a script named 'gdmd' which has the
410 same
411 interface as the Digital Mars dmd.<br>
416 <br>
421 The mapping from DMD options to GCC is as follows:<br>
431 <tbody>
436 <tr>
446 </td>
456 </td>
461 </tr>
466 <tr>
476 </td>
486 </td>
491 </tr>
496 <tr>
506 </td>
516 </td>
521 </tr>
526 <tr>
536 </td>
546 </td>
551 </tr>
556 <tr>
571 </tr>
576 <tr>
586 </td>
596 </td>
601 </tr>
606 <tr>
616 </td>
626 </td>
631 </tr>
636 <tr>
646 </td>
656 </td>
661 </tr>
666 <tr>
676 </td>
687 </td>
692 </tr>
695 <tr>
699 </td>
703 </td>
705 </tr>
707 <tr>
717 </td>
727 </td>
732 </tr>
737 <tr>
747 </td>
753 inlining (may not be
754 equivalent)<br>
759 </td>
764 </tr>
769 <tr>
779 </td>
789 </td>
794 </tr>
799 <tr>
809 </td>
815 the wrapper
816 script<br>
821 </td>
826 </tr>
831 <tr>
847 </td>
852 </tr>
857 <tr>
867 </td>
873 the wrapper
874 script<br>
879 </td>
884 </tr>
889 <tr>
899 </td>
905 for
906 profiling
907 options)</td>
912 </tr>
917 <tr>
927 </td>
937 </td>
942 </tr>
947 <tr>
957 </td>
967 </td>
972 </tr>
977 <tr>
987 </td>
993 the wrapper
994 script</td>
999 </tr>
1004 <tr>
1014 </td>
1024 </td>
1029 </tr>
1034 <tr>
1044 </td>
1054 </td>
1059 </tr>
1064 <tr>
1074 </td>
1084 </td>
1089 </tr>
1094 <tr>
1105 </td>
1116 </td>
1121 </tr>
1129 </tbody>
1130 </table>
1135 <br>
1140 Other options:<br>
1150 <tbody>
1155 <tr>
1165 </td>
1171 bounds checking<br>
1176 </td>
1181 </tr>
1186 <tr>
1196 -f[no-]emit-templates<br>
1201 </td>
1207 not template
1208 code is emitted.<br>
1213 <br>
1218 "normal" -- Emit templates, expecting multiple copies to be merged by
1219 the
1220 linker.<br>
1225 "private" -- Emit templates, but make them private to the translation
1226 unit. The executable will have multiple copies of code and
1227 data.<br>
1233 Do
1234 this even if they would not normally be emitted.<br>
1250 <br>
1265 </td>
1270 </tr>
1275 <tr>
1285 </td>
1291 file on the
1292 command line, semantically process each file preceding it.
1293 Use
1294 this if
1295 compilation errors occur due to complicated circular module
1301 </td>
1306 </tr>
1311 <tr>
1321 </td>
1327 text and
1334 </td>
1339 </tr>
1347 </tbody>
1348 </table>
1361 GDC implements a GCC extension that allows inline assembler with D
1362 expression operands. It is available on nearly all targets, not
1363 just i386. The syntax differs from the C language extension in
1364 the follow ways.
1365 <ul>
1369 <li>Statements start with '<span style="font-family: monospace;">asm { ...</span>', just like the regular DMD inline assembler.</li>
1377 <li>Instruction templates can be compile-time string constants, not
1378 just string literals. If the template is not a string literal,
1379 use parenthesis to indicate that it is not an opcode.</li>
1383 </ul>
1387 Unlike i386 inline assembler statements, extended assembler statements do not prevent a function from being inlined.<br>
1391 <br>
1395 See the GCC manual for more information about this extension.<br>
1399 <br>
1403 Example:<br>
1407 <br>
1411 <div style="margin-left: 40px;"><span style="font-family: monospace;">uint invert(uint v)</span><br style="font-family: monospace;">
1419 <span style="font-family: monospace;"> uint result;</span><br style="font-family: monospace;">
1423 <span style="font-family: monospace;"> version(X86)</span><br style="font-family: monospace;">
1427 <span style="font-family: monospace;"> asm{ "notl %[iov]" : [iov] "=r" result : "0" v; }</span><br style="font-family: monospace;">
1431 <span style="font-family: monospace;"> else version(PPC)</span><br style="font-family: monospace;">
1435 <span style="font-family: monospace;"> asm{ "nor %[oresult],%[iv],%[iv]" : [oresult] "=r" result : [iv] "r" v; }</span><br style="font-family: monospace;">
1439 <span style="font-family: monospace;"> return result;</span><br style="font-family: monospace;">
1447 </div>
1455 (This extension is a work in progress.)<br>
1459 <br>
1463 GDC implements the GCC <span style="font-family: monospace;">__attribute__</span> extension with two pragmas:<br>
1467 <br>
1471 <span style="font-family: monospace;"><span style="font-weight: bold;">pragma</span>(<span style="font-weight: bold;">GNU_attribute</span>,<span style="font-style: italic;"> name1</span>(<span style="font-style: italic;">arg1</span>, <span style="font-style: italic;">arg2</span>, ...), ...) <span style="font-style: italic;">declarations</span>...</span><br style="font-family: monospace;">
1475 <br>
1479 <span style="font-family: monospace;"><span style="font-weight: bold;">pragma</span>(<span style="font-weight: bold;">GNU_set_attribute</span>, <span style="font-style: italic;">symbol</span>, <span style="font-style: italic;">name1</span>(<span style="font-style: italic;">arg1</span>, <span style="font-style: italic;">arg2</span>...), ...);</span><br>
1483 <br>
1487 If an attribute has no arguments, the argument list may be omitted.<br>
1491 <br>
1495 The first form applies to declarations directly contained in the
1497 GCC manual for a list of attributes that can be set. Not all
1498 attributes are supported yet by GDC. Also, the interaction
1499 between these extended attributes and D languge attributes (alignment,
1500 for example) is not well defined.
1504 <ul>
1511 </ul>
1513 <ul>
1518 </ul>
1520 <ul>
1527 </ul>
1529 <ul>
1534 </ul>
1536 <ul>
1542 </ul>
1544 <ul>
1554 </ul>
1556 <ul>
1561 <ul>
1566 </li>
1571 </ul>
1576 <ul>
1579 </li>
1582 </li>
1586 </ul>
1587 </ul>
1589 <ul>
1594 <ul>
1595 <li>Mixed complex/float operations on GCC 4.0 (<a href="http://www.digitalmars.com/drn-bin/wwwnews?D.gnu/1485">D.gnu/1485</a>)</li>
1597 <li>Foreach/nested functions in templates (<a href="http://www.digitalmars.com/drn-bin/wwwnews?D.gnu/1514">D.gnu/1514</a>)</li>
1598 <li>Use correct default initializer when allocating arrays of
1599 typedef'd types</li>
1600 <li>Recursive calls to nested functions (<a href="http://www.digitalmars.com/drn-bin/wwwnews?D.gnu/1525">D.gnu/1525</a>)</li>
1604 </ul>
1609 <ul>
1611 </li>
1615 </ul>
1616 </ul>
1618 <ul>
1623 <ul>
1626 <li>ICE on nested foreach statements (<a href="http://www.digitalmars.com/drn-bin/wwwnews?D.gnu/1393">D.gnu/1393</a>)</li>
1631 <ul>
1636 </ul>
1640 <ul>
1641 <li>Spurious error on scaled register without a base
1642 register</li>
1643 <li>Access to locals by var+ofs[EBP] now works with
1644 optimization.</li>
1649 </ul>
1651 </li>
1655 </ul>
1660 <ul>
1664 <li>Support compiling multiple sources to a single object
1665 with GCC
1667 </li>
1671 </ul>
1672 </ul>
1673 <br>
1677 </div>
1678 <br>
1680 <ul>
1685 <ul>
1688 </li>
1692 </ul>
1697 <ul>
1699 </li>
1703 </ul>
1704 </ul>
1705 <br>
1707 <ul>
1712 <ul>
1717 </ul>
1722 <ul>
1726 checks.<br>
1727 </li>
1731 </ul>
1732 </ul>
1734 <ul>
1739 <ul>
1743 </li>
1747 </ul>
1748 </ul>
1750 <ul>
1755 <ul>
1760 </li>
1762 <li>DStress catch_01, catch_02, new_04, switch_19, throw_02,
1763 and
1764 others.</li>
1768 </ul>
1773 <ul>
1778 </li>
1782 </ul>
1787 <ul>
1790 conflicts with
1791 DMD.</li>
1796 <ul>
1798 <li>Looks for gdc in its own directory instead of searching
1799 the
1800 path</li>
1802 </li>
1806 </ul>
1810 </ul>
1811 </ul>
1813 <ul>
1818 <ul>
1825 </ul>
1830 <ul>
1834 </li>
1836 Only MingGW
1837 is supported out-of-the-box, however.</li>
1841 </ul>
1842 </ul>
1866 <br>
1886 <br>
1898 Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA<br>
1903 </body>
1904 </html>