|
Archives
D Programming
digitalmars.Ddigitalmars.D.bugs digitalmars.D.dtl digitalmars.D.ide digitalmars.D.dwt digitalmars.D.announce digitalmars.D.learn digitalmars.D.debugger D.gnu D C/C++ Programming
c++c++.announce c++.atl c++.beta c++.chat c++.command-line c++.dos c++.dos.16-bits c++.dos.32-bits c++.idde c++.mfc c++.rtl c++.stl c++.stl.hp c++.stl.port c++.stl.sgi c++.stlsoft c++.windows c++.windows.16-bits c++.windows.32-bits c++.wxwindows digitalmars.empire digitalmars.DMDScript electronics |
digitalmars.D.announce - Re: D compiler as part of GCC
Jerry Quinn Wrote:[also posted to D.gnu] Hi, folks, I'm interested in creating a D front end for GCC that would be part of the GCC codebase. My feeling is that a GDC that is part of GCC distributions will likely have more life than one that must be updated whenever a new GCC release comes out. As with linux kernel in-tree drivers being kept up to date, an integrated GDC would tend to move forward as well. To do this though, copyright on the code must be assigned to the FSF. This means that even though the DMD front end sources are licensed under the GPL, they cannot be directly used to write this front end as the copyright is owned by DigitalMars. Everyone who contributes code must not look at the DMD compiler source code to avoid accidentally contributing code illegally. Therefore, this will be a completely new implementation of D. The obvious disadvantage of doing this is that it will be a slow process to get to a working D compiler. However, one advantage to the D world is firming up and validating the language specification so that the language is not defined by what the DMD compiler does. My personal desire is to implement (and track) the 2.0 language since I would like to see that feature set available through GCC. Second, by the time a working front end becomes part of GCC, the 2.0 language will likely be complete. One question I have (of many) is whether a different name should be used. If this is called GDC there will be some confusion with the current GDC. What thoughts do you all have? In general is there interest in this project, especially contributing to it? Thanks, Jerry Jan 27 2010
Eldar Insafutdinov wrote:Jerry Quinn Wrote:[also posted to D.gnu] Hi, folks, I'm interested in creating a D front end for GCC that would be part of the GCC codebase. My feeling is that a GDC that is part of GCC distributions will likely have more life than one that must be updated whenever a new GCC release comes out. As with linux kernel in-tree drivers being kept up to date, an integrated GDC would tend to move forward as well. To do this though, copyright on the code must be assigned to the FSF. This means that even though the DMD front end sources are licensed under the GPL, they cannot be directly used to write this front end as the copyright is owned by DigitalMars. Everyone who contributes code must not look at the DMD compiler source code to avoid accidentally contributing code illegally. Therefore, this will be a completely new implementation of D. The obvious disadvantage of doing this is that it will be a slow process to get to a working D compiler. However, one advantage to the D world is firming up and validating the language specification so that the language is not defined by what the DMD compiler does. My personal desire is to implement (and track) the 2.0 language since I would like to see that feature set available through GCC. Second, by the time a working front end becomes part of GCC, the 2.0 language will likely be complete. One question I have (of many) is whether a different name should be used. If this is called GDC there will be some confusion with the current GDC. What thoughts do you all have? In general is there interest in this project, especially contributing to it? Thanks, Jerry Jan 27 2010
Andrei Alexandrescu Wrote:Eldar Insafutdinov wrote:Jerry Quinn Wrote:[also posted to D.gnu] Hi, folks, I'm interested in creating a D front end for GCC that would be part of the GCC codebase. My feeling is that a GDC that is part of GCC distributions will likely have more life than one that must be updated whenever a new GCC release comes out. As with linux kernel in-tree drivers being kept up to date, an integrated GDC would tend to move forward as well. To do this though, copyright on the code must be assigned to the FSF. This means that even though the DMD front end sources are licensed under the GPL, they cannot be directly used to write this front end as the copyright is owned by DigitalMars. Everyone who contributes code must not look at the DMD compiler source code to avoid accidentally contributing code illegally. Therefore, this will be a completely new implementation of D. The obvious disadvantage of doing this is that it will be a slow process to get to a working D compiler. However, one advantage to the D world is firming up and validating the language specification so that the language is not defined by what the DMD compiler does. My personal desire is to implement (and track) the 2.0 language since I would like to see that feature set available through GCC. Second, by the time a working front end becomes part of GCC, the 2.0 language will likely be complete. One question I have (of many) is whether a different name should be used. If this is called GDC there will be some confusion with the current GDC. What thoughts do you all have? In general is there interest in this project, especially contributing to it? Thanks, Jerry Jan 27 2010
Eldar Insafutdinov wrote:Andrei Alexandrescu Wrote:Eldar Insafutdinov wrote:Google's Go will be in GCC. http://gcc.gnu.org/ml/gcc/2010-01/msg00500.html . They are pushing it very hard. Jan 27 2010
Leandro Lucarella wrote:Andrei Alexandrescu, el 27 de enero a las 17:40 me escribiste:Eldar Insafutdinov wrote:Andrei Alexandrescu Wrote:Eldar Insafutdinov wrote:Google's Go will be in GCC. http://gcc.gnu.org/ml/gcc/2010-01/msg00500.html . They are pushing it very hard. Jan 28 2010
Leandro Lucarella wrote:Andrei Alexandrescu, el 28 de enero a las 09:49 me escribiste:Just see the next message: http://gcc.gnu.org/ml/gcc/2010-01/msg00501.html 2010-01-26 Ian Lance Taylor <iant google.com> * MAINTAINERS: Add myself as Go frontend maintainer. If you think Google is not pushing Go, think again... Jan 28 2010
On 01/27/2010 03:40 PM, Eldar Insafutdinov wrote:Google's Go will be in GCC. http://gcc.gnu.org/ml/gcc/2010-01/msg00500.html . They are pushing it very hard. Jan 27 2010
On 1/27/2010 5:56 PM, Ellery Newcomer wrote:On 01/27/2010 03:40 PM, Eldar Insafutdinov wrote:Google's Go will be in GCC. <http://gcc.gnu.org/ml/gcc/2010-01/msg00500.html>. Jan 27 2010
On 01/27/2010 11:24 PM, Joel C. Salomon wrote:On 1/27/2010 5:56 PM, Ellery Newcomer wrote:On 01/27/2010 03:40 PM, Eldar Insafutdinov wrote:Google's Go will be in GCC.<http://gcc.gnu.org/ml/gcc/2010-01/msg00500.html>. Jan 27 2010
Andrei Alexandrescu, el 27 de enero a las 17:40 me escribiste:Eldar Insafutdinov wrote:Andrei Alexandrescu Wrote:Eldar Insafutdinov wrote:Google's Go will be in GCC. http://gcc.gnu.org/ml/gcc/2010-01/msg00500.html . They are pushing it very hard. Jan 28 2010
Andrei Alexandrescu, el 28 de enero a las 09:49 me escribiste:Just see the next message: http://gcc.gnu.org/ml/gcc/2010-01/msg00501.html 2010-01-26 Ian Lance Taylor <iant google.com> * MAINTAINERS: Add myself as Go frontend maintainer. If you think Google is not pushing Go, think again... Jan 28 2010
Andrei Alexandrescu, el 28 de enero a las 12:29 me escribiste:Leandro Lucarella wrote:Andrei Alexandrescu, el 28 de enero a las 09:49 me escribiste:Just see the next message: http://gcc.gnu.org/ml/gcc/2010-01/msg00501.html 2010-01-26 Ian Lance Taylor <iant google.com> * MAINTAINERS: Add myself as Go frontend maintainer. If you think Google is not pushing Go, think again... Jan 28 2010
|