At

https://github.com/D-Programming-GDC/GDC/commits/master

there's the heading

"This repository has been archived by the owner. It is now read-only."

Where will the development of GDC continue?

On Thursday, 21 March 2019 at 08:19:56 UTC, Per Nordlöw wrote:
> At
>
> https://github.com/D-Programming-GDC/GDC/commits/master
>
> there's the heading
>
> "This repository has been archived by the owner. It is now read-only."
>
> Where will the development of GDC continue?

We use https://github.com/D-Programming-GDC/gcc for CI, but commits will go to the GCC SVN first, so GCC SVN or snapshot tarballs is the recommended way to get the latest GDC.

There is one exception: When GCC development is in feature freeze, we might provide newer DMD frontends in a gdc-next branch at https://github.com/D-Programming-GDC/gcc . However, so far we have not set up this branch, this will probably happen in the next two weeks. Maybe I'll also provide DDMD-FE backports for GCC9 in that repo, but I'm not sure yet. The latest DDMD-FE is somewhere in the archived repos, but it hasn't been updated for some time.

On Thursday, 21 March 2019 at 08:19:56 UTC, Per Nordlöw wrote:
> At
>
> https://github.com/D-Programming-GDC/GDC/commits/master
>
> there's the heading
>
> "This repository has been archived by the owner. It is now read-only."
>
> Where will the development of GDC continue?

I am not exactly sure, but if GDC got merged into GCC, doesn't that mean that any new development will be done on the GCC repository?

On 3/21/19 6:01 AM, Johannes Pfau wrote:
> On Thursday, 21 March 2019 at 08:19:56 UTC, Per Nordlöw wrote:
>> At
>>
>> https://github.com/D-Programming-GDC/GDC/commits/master
>>
>> there's the heading
>>
>> "This repository has been archived by the owner. It is now read-only."
>>
>> Where will the development of GDC continue?
> 
> We use https://github.com/D-Programming-GDC/gcc for CI, but commits will go to the GCC SVN first, so GCC SVN or snapshot tarballs is the recommended way to get the latest GDC.
> 
> There is one exception: When GCC development is in feature freeze, we might provide newer DMD frontends in a gdc-next branch at https://github.com/D-Programming-GDC/gcc . However, so far we have not set up this branch, this will probably happen in the next two weeks. Maybe I'll also provide DDMD-FE backports for GCC9 in that repo, but I'm not sure yet. The latest DDMD-FE is somewhere in the archived repos, but it hasn't been updated for some time.

Thanks -- I also tried to figure out how to install GDC just yesterday and gave up. All wiki links and google top results seemed dead ends.

On 3/21/19 6:51 PM, James Blachly wrote:
> On 3/21/19 6:01 AM, Johannes Pfau wrote:
>> On Thursday, 21 March 2019 at 08:19:56 UTC, Per Nordlöw wrote:
>>> At
>>>
>>> https://github.com/D-Programming-GDC/GDC/commits/master
>>>
>>> there's the heading
>>>
>>> "This repository has been archived by the owner. It is now read-only."
>>>
>>> Where will the development of GDC continue?
>>
>> We use https://github.com/D-Programming-GDC/gcc for CI, but commits will go to the GCC SVN first, so GCC SVN or snapshot tarballs is the recommended way to get the latest GDC.
>>
>> There is one exception: When GCC development is in feature freeze, we might provide newer DMD frontends in a gdc-next branch at https://github.com/D-Programming-GDC/gcc . However, so far we have not set up this branch, this will probably happen in the next two weeks. Maybe I'll also provide DDMD-FE backports for GCC9 in that repo, but I'm not sure yet. The latest DDMD-FE is somewhere in the archived repos, but it hasn't been updated for some time.
> 
> Thanks -- I also tried to figure out how to install GDC just yesterday and gave up. All wiki links and google top results seemed dead ends.
> 

A little bit of further information: the downloads listed on

https://gdcproject.org/downloads

are 2016 versions.

On Thursday, 21 March 2019 at 22:51:21 UTC, James Blachly wrote:

> Thanks -- I also tried to figure out how to install GDC just yesterday and gave up. All wiki links and google top results seemed dead ends.

I'm also a little puzzled by how GDC is structured, but I have learned a few things with the help of some of the GDC developers, and I'll share my understanding below (though be aware that my assumptions may be wrong).

GDC is in a weird state right now where it needs to boostrap itself.  The bootstrap compiler has a front-end written in C++, but the lastest GDC on GitHub has a front-end written in D.

My understanding is that this bootstrap compiler with the front-end written in C++ is what is being released with GCC 9.  Since GCC always needs to be able to be built with a prior version of GCC, GCC 10 will be the first release with the latest D frontend.

So, to build your own GDC compiler, you need to first build the bootstrap compiler.  I have a script for that at https://github.com/JinShil/native-gdc

Then, using the bootstrap compiler, you can build the latest GDC with the D frontend from GitHub.  I have a script for that too, but it is only for building an ARM cross-compiler.  See https://github.com/JinShil/arm-none-eabi-gdc

Mike