Lines Matching full:code
15 see <a href="https://code.google.com/p/gofrontend/source/browse/HACKING">the
24 libgo library. Code that is part of GCC rather than gccgo must follow
29 <h2>Code</h2>
39 the GCC source code repository hosted at <code>gcc.gnu.org</code>. In
40 the <code>gofrontend</code> repository, the <code>go</code> directory
41 is mirrored to the <code>gcc/go/gofrontend</code> directory in the GCC
42 repository, and the <code>gofrontend</code> <code>libgo</code>
43 directory is mirrored to the GCC <code>libgo</code> directory. In
44 addition, the <code>test</code> directory
46 is mirrored to the <code>gcc/testsuite/go.test/test</code> directory
60 In writing code for the frontend, follow the formatting of the
61 surrounding code.
62 Almost all GCC-specific code is not in the frontend proper and is
63 instead in the GCC sources in the <code>gcc/go</code> directory.
69 The library code in the Go repository is periodically merged into
70 the <code>libgo/go</code> directory of the <code>gofrontend</code> and
72 script <code>libgo/merge.sh</code>. Accordingly, most library changes
74 of <code>libgo/go</code> are gccgo-specific; that said, some of the
75 files in <code>libgo/runtime</code> are based on files
76 in <code>src/runtime</code> in the main Go repository.
87 To run the gccgo test suite, run <code>make check-go</code> in your
89 under <code>gcc/testsuite/go.*</code> and will also run
90 the <code>libgo</code> testsuite. This copy of the tests from the
92 in <code>gcc/testsuite/go.test/go-test.exp</code>.
99 the <code>gcc/testsuite/go.go-torture</code>
100 or <code>gcc/testsuite/go.dg</code> directories in the GCC repository.
107 main Go repository, only for the <code>gofrontend</code> project and
108 the <code>gofrontend-dev@googlegroups.com</code> mailing list
109 rather than the <code>go</code> project and the
110 <code>golang-dev@googlegroups.com</code> mailing list. Those changes
