www.digitalmars.com         C & C++   DMDScript  

D.gnu - Roadmap

reply Iain Buclaw <ibuclaw ubuntu.com> writes:
Started an initial list for our roadmap for the next month.

https://bitbucket.org/goshawk/gdc/wiki/Roadmap


Daniel, if there's anything you could help on, please don't hesitate to
contact me. :)


Regards
Iain
Jan 23 2012
next sibling parent "Jesse Phillips" <jessekphillips+D gmail.com> writes:
On Monday, 23 January 2012 at 20:13:26 UTC, Iain Buclaw wrote:
 Started an initial list for our roadmap for the next month.

 https://bitbucket.org/goshawk/gdc/wiki/Roadmap


 Daniel, if there's anything you could help on, please don't 
 hesitate to
 contact me. :)


 Regards
 Iain

There is a plan for GCC 4.8 to contain D support. Is anything still blocking that, or is it going to be ready soon?
Jan 25 2012
prev sibling next sibling parent Andrew Wiley <wiley.andrew.j gmail.com> writes:
On Wed, Jan 25, 2012 at 3:48 PM, Jesse Phillips
<jessekphillips+D gmail.com> wrote:
 On Monday, 23 January 2012 at 20:13:26 UTC, Iain Buclaw wrote:
 Started an initial list for our roadmap for the next month.

 https://bitbucket.org/goshawk/gdc/wiki/Roadmap


 Daniel, if there's anything you could help on, please don't hesitate to
 contact me. :)


 Regards
 Iain

There is a plan for GCC 4.8 to contain D support. Is anything still blocking that, or is it going to be ready soon?

That's why the last entry in the roadmap he gave a link to is "Submit GDC for inclusion in GCC" The roadmap is pretty much the answer to your question.
Jan 25 2012
prev sibling next sibling parent "Jesse Phillips" <jessekphillips+D gmail.com> writes:
 That's why the last entry in the roadmap he gave a link to is 
 "Submit
 GDC for inclusion in GCC"
 The roadmap is pretty much the answer to your question.

Heh, I'd gleamed that and went to re-read that and just read the second to last: "Submit all patches to GCC proper for inclusion in GCC." and just thought my first read was wrong.
Jan 25 2012
prev sibling next sibling parent Iain Buclaw <ibuclaw ubuntu.com> writes:
On 25 January 2012 22:22, Jesse Phillips <jessekphillips+D gmail.com> wrote:
 That's why the last entry in the roadmap he gave a link to is "Submit
 GDC for inclusion in GCC"
 The roadmap is pretty much the answer to your question.

Heh, I'd gleamed that and went to re-read that and just read the second to last: "Submit all patches to GCC proper for inclusion in GCC." and just thought my first read was wrong.

All alterations to GCC that are required for D need to be submitted separately. As it currently stands, this will be x86 support for 'naked' functions, and something along the description of callee_pop_float_return. -- Iain Buclaw *(p < e ? p++ : p) = (c & 0x0f) + '0';
Jan 25 2012
prev sibling next sibling parent reply Johannes Pfau <nospam example.com> writes:
Am Mon, 23 Jan 2012 20:13:26 +0000 (UTC)
schrieb Iain Buclaw <ibuclaw ubuntu.com>:

 Started an initial list for our roadmap for the next month.
 
 https://bitbucket.org/goshawk/gdc/wiki/Roadmap
 
 
 Daniel, if there's anything you could help on, please don't hesitate
 to contact me. :)
 
 
 Regards
 Iain

"Re-structure project directories to match that of GCC" can you give some more information about that? Will druntime, phobos1 and phobos2 all get own subdirectories in the gcc folder? I'll try to make druntime buildable out-of-tree, so it'd be good to know. Btw: when gdc moves to git(hub), will we have separate repositories for druntime & phobos? This way we could make the gdc druntime/phobos forks of the dmd repositories and pushing changes upstream should be easier.
Feb 13 2012
next sibling parent reply Iain Buclaw <ibuclaw ubuntu.com> writes:
On 13 February 2012 18:46, Johannes Pfau <nospam example.com> wrote:
 Am Mon, 23 Jan 2012 20:13:26 +0000 (UTC)
 schrieb Iain Buclaw <ibuclaw ubuntu.com>:

 Started an initial list for our roadmap for the next month.

 https://bitbucket.org/goshawk/gdc/wiki/Roadmap


 Daniel, if there's anything you could help on, please don't hesitate
 to contact me. :)


 Regards
 Iain

"Re-structure project directories to match that of GCC" can you give some more information about that? Will druntime, phobos1 and phobos2 all get own subdirectories in the gcc folder? I'll try to make druntime buildable out-of-tree, so it'd be good to know.

Yeah, D1 and D2 will have to be split from each other, as the library folders share the same name, thus conflict. The new directory structure will be: / ... /gcc ... ... /d ... ... ... /dfrontend ... /libphobos ... ... /core ... ... /etc ... ... /gc ... ... /gcc ... ... /rt ... ... /std
 Btw: when gdc moves to git(hub), will we have separate repositories for
 druntime & phobos? This way we could make the gdc druntime/phobos forks
 of the dmd repositories and pushing changes upstream should be easier.

The problem with this is, if you are building gdc, you have to clone/download THREE repositories/tarballs and move/extract them to the correct places, which are in varying locations in the gcc source code. -- Iain Buclaw *(p < e ? p++ : p) = (c & 0x0f) + '0';
Feb 13 2012
parent Jacob Carlborg <doob me.com> writes:
On 2012-02-13 22:41, Leandro Lucarella wrote:
 Johannes Pfau, el 13 de febrero a las 20:57 me escribiste:
 The problem with this is, if you are building gdc, you have to
 clone/download THREE repositories/tarballs and move/extract them to
 the correct places, which are in varying locations in the gcc source
 code.

Git submodules might be useful here, that's what the ldc developers do. See https://github.com/ldc-developers/ldc/tree/master/runtime but I have to admit I don't know anything about git submodules.

Git submodules can definitely take care of this. Of course is a little more tedious to use than having just a plain monolithic repo, but it's not that bad.

I'm not sure they will help if you have to do this: "and move/extract them to the correct places, which are in varying locations in the gcc source code" It might help somewhat but not completely. -- /Jacob Carlborg
Feb 13 2012
prev sibling next sibling parent Iain Buclaw <ibuclaw ubuntu.com> writes:
On 13 February 2012 18:46, Johannes Pfau <nospam example.com> wrote:
 Btw: when gdc moves to git(hub), will we have separate repositories for
 druntime & phobos? This way we could make the gdc druntime/phobos forks
 of the dmd repositories and pushing changes upstream should be easier.

I created a new repository here: https://github.com/ibuclaw/gdc Though I'm not so sure about having my login account attached to it, so may will create a new account dedicated for it. -- Iain Buclaw *(p < e ? p++ : p) = (c & 0x0f) + '0';
Feb 13 2012
prev sibling parent Iain Buclaw <ibuclaw ubuntu.com> writes:
On 15 February 2012 18:21, Johannes Pfau <nospam example.com> wrote:
 Am Mon, 13 Feb 2012 19:30:07 +0000
 schrieb Iain Buclaw <ibuclaw ubuntu.com>:

 On 13 February 2012 18:46, Johannes Pfau <nospam example.com> wrote:
 Am Mon, 23 Jan 2012 20:13:26 +0000 (UTC)
 schrieb Iain Buclaw <ibuclaw ubuntu.com>:

 Started an initial list for our roadmap for the next month.

 https://bitbucket.org/goshawk/gdc/wiki/Roadmap


 Daniel, if there's anything you could help on, please don't
 hesitate to contact me. :)


 Regards
 Iain

"Re-structure project directories to match that of GCC" can you give some more information about that? Will druntime, phobos1 and phobos2 all get own subdirectories in the gcc folder? I'll try to make druntime buildable out-of-tree, so it'd be good to know.

Yeah, D1 and D2 will have to be split from each other, as the library folders share the same name, thus conflict. The new directory structure will be: / ... /gcc ... ... /d ... ... ... /dfrontend ... /libphobos ... ... /core ... ... /etc ... ... /gc ... ... /gcc ... ... /rt ... ... /std

Is there a special reason why you want to keep druntime & phobos in one directory? If you just don't have the time to split druntime & phobos, I could do it. I've already partially done this when adding support for out-of-tree builds to druntime (That's working now, but I need a little more time to clean up the patches and test multilib)

That is how it currently looks in the GCC source directories once you get past the ./setup-gcc.sh stage. It would be great if druntime was a subdirectory, so if you have time to do this before I get round to it, patches to the configure scripts are always welcome. :-) -- Iain Buclaw *(p < e ? p++ : p) = (c & 0x0f) + '0';
Feb 15 2012
prev sibling next sibling parent Johannes Pfau <nospam example.com> writes:
Am Mon, 13 Feb 2012 19:30:07 +0000
schrieb Iain Buclaw <ibuclaw ubuntu.com>:

 On 13 February 2012 18:46, Johannes Pfau <nospam example.com> wrote:
 Am Mon, 23 Jan 2012 20:13:26 +0000 (UTC)
 schrieb Iain Buclaw <ibuclaw ubuntu.com>:

 Started an initial list for our roadmap for the next month.

 https://bitbucket.org/goshawk/gdc/wiki/Roadmap


 Daniel, if there's anything you could help on, please don't
 hesitate to contact me. :)


 Regards
 Iain

"Re-structure project directories to match that of GCC" can you give some more information about that? Will druntime, phobos1 and phobos2 all get own subdirectories in the gcc folder? I'll try to make druntime buildable out-of-tree, so it'd be good to know.

Yeah, D1 and D2 will have to be split from each other, as the library folders share the same name, thus conflict. The new directory structure will be: / ... /gcc ... ... /d ... ... ... /dfrontend ... /libphobos ... ... /core ... ... /etc ... ... /gc ... ... /gcc ... ... /rt ... ... /std
 Btw: when gdc moves to git(hub), will we have separate repositories
 for druntime & phobos? This way we could make the gdc
 druntime/phobos forks of the dmd repositories and pushing changes
 upstream should be easier.

The problem with this is, if you are building gdc, you have to clone/download THREE repositories/tarballs and move/extract them to the correct places, which are in varying locations in the gcc source code.

Git submodules might be useful here, that's what the ldc developers do. See https://github.com/ldc-developers/ldc/tree/master/runtime but I have to admit I don't know anything about git submodules.
Feb 13 2012
prev sibling next sibling parent Leandro Lucarella <luca llucax.com.ar> writes:
Johannes Pfau, el 13 de febrero a las 20:57 me escribiste:
 The problem with this is, if you are building gdc, you have to
 clone/download THREE repositories/tarballs and move/extract them to
 the correct places, which are in varying locations in the gcc source
 code.

Git submodules might be useful here, that's what the ldc developers do. See https://github.com/ldc-developers/ldc/tree/master/runtime but I have to admit I don't know anything about git submodules.

Git submodules can definitely take care of this. Of course is a little more tedious to use than having just a plain monolithic repo, but it's not that bad. -- Leandro Lucarella (AKA luca) http://llucax.com.ar/ ---------------------------------------------------------------------- GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145 104C 949E BFB6 5F5A 8D05) ---------------------------------------------------------------------- 3 people die every year, testing if a 9 volts battery works on their tongue
Feb 13 2012
prev sibling parent Johannes Pfau <nospam example.com> writes:
Am Mon, 13 Feb 2012 19:30:07 +0000
schrieb Iain Buclaw <ibuclaw ubuntu.com>:

 On 13 February 2012 18:46, Johannes Pfau <nospam example.com> wrote:
 Am Mon, 23 Jan 2012 20:13:26 +0000 (UTC)
 schrieb Iain Buclaw <ibuclaw ubuntu.com>:

 Started an initial list for our roadmap for the next month.

 https://bitbucket.org/goshawk/gdc/wiki/Roadmap


 Daniel, if there's anything you could help on, please don't
 hesitate to contact me. :)


 Regards
 Iain

"Re-structure project directories to match that of GCC" can you give some more information about that? Will druntime, phobos1 and phobos2 all get own subdirectories in the gcc folder? I'll try to make druntime buildable out-of-tree, so it'd be good to know.

Yeah, D1 and D2 will have to be split from each other, as the library folders share the same name, thus conflict. The new directory structure will be: / ... /gcc ... ... /d ... ... ... /dfrontend ... /libphobos ... ... /core ... ... /etc ... ... /gc ... ... /gcc ... ... /rt ... ... /std

Is there a special reason why you want to keep druntime & phobos in one directory? If you just don't have the time to split druntime & phobos, I could do it. I've already partially done this when adding support for out-of-tree builds to druntime (That's working now, but I need a little more time to clean up the patches and test multilib)
Feb 15 2012