From: Ian Lance Taylor <iant@google.com>
To: Iain Buclaw <ibuclaw@ubuntu.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Merging gdc (GNU D Compiler) into gcc
Date: Wed, 05 Oct 2011 00:59:00 -0000 [thread overview]
Message-ID: <mcr62k4nyiz.fsf@coign.corp.google.com> (raw)
In-Reply-To: <CABOHX+f63imd7rkTSTR+N0p2_KPttn4gED-pxx0qfFiSyaPjAQ@mail.gmail.com> (Iain Buclaw's message of "Tue, 4 Oct 2011 20:30:32 +0100")
Iain Buclaw <ibuclaw@ubuntu.com> writes:
> The active development of the D frontend would continue to be mirrored
> in an external repository, but will occasionally be merged into GDC
> project.
Well, Go does set a precedent for this. The main issue here is that
this means that there is (another) directory containing source code that
the gcc maintainers can't update. This is workable if the D frontend
does not #include any gcc header files or call any gcc functions. That
is, if it is truly standalone. (The Go frontend is not yet in this
state, although I am slowly working toward it.)
> Some work would need to be done on naked functions at least first so
> that changes required are only to gcc/config. I would be grateful if I
> could get pointed in the right direction for implementing naked as a
> function attribute for i386 so all frontends could benefit.
Needs a target hook in target.def and a new attribute probably in
c-family/c-common.c. The new attribute would check the target hook to
see whether the backend supports it.
>> The D runtime appears to be in a subdirectory of gcc/d. Ordinarily we
>> would prefer that it be in a separate toplevel directory, e.g.,
>> libdruntime.
>>
>
> The set-up build script that is provided with the gdc development
> folder makes symlinks from gcc/d/ to a libphobos toplevel directory.
That is kind of awkward, though--why not just set up libphobos in the
first place? I understand this may require two directories to be
mirrored.
> First question that pops up after having a quick look is, are there
> any tips around for writing the scripts for the testsuite? I'm not too
> familiar with Dejagnu, and the current testsuite used for GDC D2
> development is written in make.
DejaGNU is too horrible for me to talk about. I can't recommend
anything other than blind copying of existing scripts.
Ian
next prev parent reply other threads:[~2011-10-04 23:11 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 7:08 Iain Buclaw
2011-10-04 8:41 ` Andrew Haley
2011-10-04 18:19 ` Iain Buclaw
2011-10-06 15:15 ` Iain Buclaw
2011-10-04 14:03 ` Ian Lance Taylor
2011-10-04 19:30 ` Iain Buclaw
2011-10-04 19:37 ` Andrew Pinski
2011-10-04 20:13 ` Iain Buclaw
2011-10-04 23:11 ` Ian Lance Taylor
2011-10-04 21:41 ` David Brown
2011-10-04 21:47 ` David Brown
2011-10-04 22:51 ` Andrew Pinski
2011-10-05 9:31 ` David Brown
2011-10-05 10:00 ` David Brown
2011-10-05 12:49 ` Andi Kleen
2011-10-05 14:44 ` David Brown
2011-10-05 14:59 ` David Brown
2011-10-04 20:41 ` Tom Tromey
2011-10-05 0:59 ` Ian Lance Taylor [this message]
2011-10-05 4:14 ` Iain Buclaw
2011-10-11 14:05 ` Dave Korn
2011-10-04 16:50 ` Joseph S. Myers
2011-10-04 19:45 ` Iain Buclaw
2011-10-04 19:56 ` Joseph S. Myers
2011-10-06 8:31 ` Walter Bright
2012-04-11 14:12 ` Iain Buclaw
2012-04-13 23:01 ` Dave Korn
2012-05-10 9:37 ` Iain Buclaw
2012-05-10 9:48 ` Richard Guenther
2012-05-10 9:53 ` Iain Buclaw
2012-05-10 11:51 ` Manuel López-Ibáñez
2012-07-21 20:00 ` Florian Weimer
2012-07-24 20:37 ` Iain Buclaw
-- strict thread matches above, loose matches on Subject: below --
2010-11-08 23:13 Merging gdc (Gnu " Walter Bright
2010-11-09 1:14 ` Joseph S. Myers
2010-11-09 7:22 ` Walter Bright
2010-11-09 13:09 ` Andrew Haley
2010-11-09 13:57 ` Jakub Jelinek
2010-11-09 16:43 ` Joe Buck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mcr62k4nyiz.fsf@coign.corp.google.com \
--to=iant@google.com \
--cc=gcc@gcc.gnu.org \
--cc=ibuclaw@ubuntu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).