Re: GDC environment variable - solved, but new problem

> Re GCC 9.1, however beware of <https://gcc.gnu.org/PR104749> > "stage1 d21 fails to link with GDC 9.1". Thanks for all who replied. Thanks especially for mentioning this problem, as my build did indeed fail with this error on GCC 9.3. I applied the fix and that'

Re: GDC environment variable

et when bootstrapping >> GCC? Thanks. > > I do see make using ‘GDC' while building gcc compiler, maybe try changing > that ? Indeed 'GDC' is it. See my <https://inbox.sourceware.org/gcc-patches/87mtlk8m1m@euler.schwinge.homeip.net> for examp

Re: GDC environment variable

I expect it to be `DC`. Original Message On 7 Dec 2022, 06:11, Dave Blanchard wrote: > Is there an environment variable like 'CC' or 'CXX', which specifies the name > of the D compiler to use, which I might need to set when bootstrapping GCC? > Thanks. -- Dave Blanchard

Re: GDC environment variable

I do see make using ‘GDC' while building gcc compiler, maybe try changing that ? - Ankur > On 07-Dec-2022, at 11:42 AM, Dave Blanchard wrote: > > Is there an environment variable like 'CC' or 'CXX', which specifies the name > of the D compiler t

GDC environment variable

Is there an environment variable like 'CC' or 'CXX', which specifies the name of the D compiler to use, which I might need to set when bootstrapping GCC? Thanks. -- Dave Blanchard

Re: gccgo emits GIMPLE with temporaries for boolean expressions unlike gcc, gdc

On Wed, Aug 3, 2022 at 6:26 AM j wrote: > > I've proposed a patch [1] for condition coverage profiling in gcc, > implemented in the middle-end alongside the branch coverage. I've > written most of the tests for C and a few for C++ and finally got around > to try it with a toy example for D and go

Re: gccgo emits GIMPLE with temporaries for boolean expressions unlike gcc, gdc

CCing Go maintainer. Martin On 8/3/22 15:25, j wrote: > > Hello, > > I've proposed a patch [1] for condition coverage profiling in gcc, > implemented in the middle-end alongside the branch coverage. I've written > most of the tests for C and a few for C++ and finally got around to try it > w

gccgo emits GIMPLE with temporaries for boolean expressions unlike gcc, gdc

Hello, I've proposed a patch [1] for condition coverage profiling in gcc, implemented in the middle-end alongside the branch coverage. I've written most of the tests for C and a few for C++ and finally got around to try it with a toy example for D and go and noticed something odd about Go's

Re: Merging gdc (GNU D Compiler) into gcc

On 21 July 2012 21:00, Florian Weimer wrote: > * Iain Buclaw: > >> I've have received news from Walter Bright that the license of the D >> frontend has been assigned to the FSF. As the current maintainer of >> GDC, I would like to get this moved forward, starting wit

Re: Merging gdc (GNU D Compiler) into gcc

* Iain Buclaw: > I've have received news from Walter Bright that the license of the D > frontend has been assigned to the FSF. As the current maintainer of > GDC, I would like to get this moved forward, starting with getting the > ball rolling. What would need to be done?

Re: Merging gdc (GNU D Compiler) into gcc

On 10 May 2012 11:52, Iain Buclaw wrote: > > Thanks, would it be best to split the frontend, library, and patches > to gcc proper into three parts? >From observing how other big projects got merged, I think it is better: 1) If you have anything that can be committed independently

Re: Merging gdc (GNU D Compiler) into gcc

received news from Walter Bright that the license of the D >>>> frontend has been assigned to the FSF. As the current maintainer of >>>> GDC, I would like to get this moved forward, starting with getting the >>>> ball rolling. What would need to be done? And what are th

Re: Merging gdc (GNU D Compiler) into gcc

ntend has been assigned to the FSF. As the current maintainer of >>> GDC, I would like to get this moved forward, starting with getting the >>> ball rolling. What would need to be done? And what are the processes >>> required? (ie: passing the project through to technical review

Re: Merging gdc (GNU D Compiler) into gcc

On 11 April 2012 15:12, Iain Buclaw wrote: > On 4 October 2011 08:08, Iain Buclaw wrote: >> Hi, >> >> I've have received news from Walter Bright that the license of the D >> frontend has been assigned to the FSF. As the current maintainer of >> GDC,

Re: Merging gdc (GNU D Compiler) into gcc

On 11/04/2012 15:12, Iain Buclaw wrote: > This has been rather long wait from my side of the pond (moving has > taken away quite some time from my side). But I'll be in a position > to begin discussion on arrangements this weekend for patches to be > submitted for GCC 4.8. > > I would be gratefu

Re: Merging gdc (GNU D Compiler) into gcc

On 4 October 2011 08:08, Iain Buclaw wrote: > Hi, > > I've have received news from Walter Bright that the license of the D > frontend has been assigned to the FSF. As the current maintainer of > GDC, I would like to get this moved forward, starting with getting the > ball r

Re: Merging gdc (GNU D Compiler) into gcc

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. >> > > :-)

Re: Merging gdc (GNU D Compiler) into gcc

On 4 October 2011 09:41, Andrew Haley wrote: > On 10/04/2011 08:08 AM, Iain Buclaw wrote: > >> I've have received news from Walter Bright that the license of the D >> frontend has been assigned to the FSF. As the current maintainer of >> GDC, I would like to get this

Re: Merging gdc (GNU D Compiler) into gcc

On 10/4/2011 12:08 AM, Iain Buclaw wrote: I've have received news from Walter Bright that the license of the D frontend has been assigned to the FSF. As the current maintainer of GDC, I would like to get this moved forward, starting with getting the ball rolling. What would need to be

Re: Merging gdc (GNU D Compiler) into gcc

On 05/10/2011 12:00, Andi Kleen wrote: David Brown writes: Some toolchains are configured to have a series of "init" sections at startup (technically, that's a matter of the default linker scripts and libraries rather than the compiler). You can get code to run at specific times during startu

Re: Merging gdc (GNU D Compiler) into gcc

David Brown writes: > > Some toolchains are configured to have a series of "init" sections at > startup (technically, that's a matter of the default linker scripts > and libraries rather than the compiler). You can get code to run at > specific times during startup by placing the instructions dir

Re: Merging gdc (GNU D Compiler) into gcc

On 04/10/2011 23:47, Andrew Pinski wrote: On Tue, Oct 4, 2011 at 2:40 PM, David Brown wrote: "naked" functions are often useful in embedded systems, and are therefore useful (and implemented) on many gcc targets. It would make sense to have the attribute available universally in gcc, if that d

Re: Merging gdc (GNU D Compiler) into gcc

On 5 October 2011 00:10, Ian Lance Taylor wrote: > Iain Buclaw 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

Re: Merging gdc (GNU D Compiler) into gcc

Iain Buclaw 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)

Re: Merging gdc (GNU D Compiler) into gcc

Iain Buclaw writes: > On 4 October 2011 20:36, Andrew Pinski wrote: >> On Tue, Oct 4, 2011 at 12:30 PM, Iain Buclaw wrote: >>> These patches address two areas of the D language: >>> 1) D calling convention. >>> 2) Naked functions on i386 and x86_64 >>> >>> Some work would need to be done on nak

Re: Merging gdc (GNU D Compiler) into gcc

On Tue, Oct 4, 2011 at 2:40 PM, David Brown wrote: > "naked" functions are often useful in embedded systems, and are therefore > useful (and implemented) on many gcc targets.  It would make sense to have > the attribute available universally in gcc, if that doesn't involve a lot of > extra work, e

Re: Merging gdc (GNU D Compiler) into gcc

On 04/10/11 21:36, Andrew Pinski wrote: On Tue, Oct 4, 2011 at 12:30 PM, Iain Buclaw wrote: These patches address two areas of the D language: 1) D calling convention. 2) Naked functions on i386 and x86_64 Some work would need to be done on naked functions at least first so that changes requir

Re: Merging gdc (GNU D Compiler) into gcc

> "Iain" == Iain Buclaw writes: Ian> There is a directory gcc/d/zlib, but gcc already has a top-level zlib Ian> directory. Iain> Zlib there is the version released with the D Phobos library, it is Iain> slightly newer. But is harmless to remove. You could alternatively update the version in

Re: Merging gdc (GNU D Compiler) into gcc

On 4 October 2011 20:36, Andrew Pinski wrote: > On Tue, Oct 4, 2011 at 12:30 PM, Iain Buclaw wrote: >> These patches address two areas of the D language: >> 1) D calling convention. >> 2) Naked functions on i386 and x86_64 >> >> Some work would need to be done on naked functions at least first so

Re: Merging gdc (GNU D Compiler) into gcc

On Tue, 4 Oct 2011, Iain Buclaw wrote: > The original copyrights for the GDC D front-end for GCC are in the > name of David Friedman, who has been MIA since 2007. Since the > project has been revived, all changes and additions have been > copyrighted in my name, Michael's, and V

Re: Merging gdc (GNU D Compiler) into gcc

On 4 October 2011 17:50, Joseph S. Myers wrote: > On Tue, 4 Oct 2011, Iain Buclaw wrote: > >> Hi, >> >> I've have received news from Walter Bright that the license of the D >> frontend has been assigned to the FSF. As the current maintainer of >> GD

Re: Merging gdc (GNU D Compiler) into gcc

On Tue, Oct 4, 2011 at 12:30 PM, Iain Buclaw wrote: > These patches address two areas of the D language: > 1) D calling convention. > 2) Naked functions on i386 and x86_64 > > Some work would need to be done on naked functions at least first so > that changes required are only to gcc/config. I wou

Re: Merging gdc (GNU D Compiler) into gcc

On 4 October 2011 15:02, Ian Lance Taylor wrote: > Iain Buclaw writes: > >> I've have received news from Walter Bright that the license of the D >> frontend has been assigned to the FSF. As the current maintainer of >> GDC, I would like to get this moved forwa

Re: Merging gdc (GNU D Compiler) into gcc

On 4 October 2011 09:41, Andrew Haley wrote: > On 10/04/2011 08:08 AM, Iain Buclaw wrote: > >> I've have received news from Walter Bright that the license of the D >> frontend has been assigned to the FSF. As the current maintainer of >> GDC, I would like to get this

Re: Merging gdc (GNU D Compiler) into gcc

On Tue, 4 Oct 2011, Iain Buclaw wrote: > Hi, > > I've have received news from Walter Bright that the license of the D > frontend has been assigned to the FSF. As the current maintainer of > GDC, I would like to get this moved forward, starting with getting the > ball roll

Re: Merging gdc (GNU D Compiler) into gcc

Iain Buclaw writes: > I've have received news from Walter Bright that the license of the D > frontend has been assigned to the FSF. As the current maintainer of > GDC, I would like to get this moved forward, starting with getting the > ball rolling. What would need to be done?

Re: Merging gdc (GNU D Compiler) into gcc

On 10/04/2011 08:08 AM, Iain Buclaw wrote: > I've have received news from Walter Bright that the license of the D > frontend has been assigned to the FSF. As the current maintainer of > GDC, I would like to get this moved forward, starting with getting the > ball rolling. What

Merging gdc (GNU D Compiler) into gcc

Hi, I've have received news from Walter Bright that the license of the D frontend has been assigned to the FSF. As the current maintainer of GDC, I would like to get this moved forward, starting with getting the ball rolling. What would need to be done? And what are the processes required

Re: Merging gdc (Gnu D Compiler) into gcc

On Tue, Nov 09, 2010 at 05:08:44AM -0800, Jakub Jelinek wrote: > On Tue, Nov 09, 2010 at 09:36:08AM +, Andrew Haley wrote: > > > The D specific part of gdc is already GPL, it's just copyrighted by > > > Digital Mars. I understand the copyright must be reassign

Re: Merging gdc (Gnu D Compiler) into gcc

On Tue, Nov 09, 2010 at 09:36:08AM +, Andrew Haley wrote: > > The D specific part of gdc is already GPL, it's just copyrighted by > > Digital Mars. I understand the copyright must be reassigned to the FSF. > > Is it possible to fork the code, and assign copyright of one

Re: Merging gdc (Gnu D Compiler) into gcc

et achieve the level of separation >> achieved by Ada, for example; there are plenty of uses of GCC's tree >> interfaces in the gofrontend/ directory that mean portability to other >> back ends is more theory than reality.) > > The D specific part of gdc is already GPL, it

Re: Merging gdc (Gnu D Compiler) into gcc

han reality.) The D specific part of gdc is already GPL, it's just copyrighted by Digital Mars. I understand the copyright must be reassigned to the FSF. Is it possible to fork the code, and assign copyright of one fork to the FSF and leave the other copyrighted by Digital Mars? In gen

Re: Merging gdc (Gnu D Compiler) into gcc

On Mon, 8 Nov 2010, Walter Bright wrote: > Who do I need to talk to in order to resolve the various licensing issues so > this becomes possible? The FSF, via the Steering Committee, via this list. The standard assignment and licensing policies are as described in the Mission Statement

Merging gdc (Gnu D Compiler) into gcc

Who do I need to talk to in order to resolve the various licensing issues so this becomes possible? Walter Bright Digital Mars http://www.digitalmars.com free C, C++, D programming language compilers

Re: GDC

On Wed, May 21, 2008 at 09:38:06PM +0400, Rohan wrote: > Is there any plan to merge GDC with GCC? Not at present. > I know that GDC package available separately, but I think it would be > much better to get in at one box. Now for adding support D language > needed to rebuild all

Re: GDC

>>>>> "Rohan" == Rohan <[EMAIL PROTECTED]> writes: Rohan> Is there any plan to merge GDC with GCC? Rohan> I know that GDC package available separately, but I think it would be Rohan> much better to get in at one box. Now for adding support D language R

GDC

Is there any plan to merge GDC with GCC? I know that GDC package available separately, but I think it would be much better to get in at one box. Now for adding support D language needed to rebuild all GCC with GDC. P.S. I talk about D language -- С уважением, Rohan

GDC

Maybe you can add gdc to your GCC front-ends listing (http://home.earthlink.net/~dvdfrdmn/d/).