Re: [PATCH 9/13] D: D2 Testsuite Dejagnu files.
On Jun 6, 2017, at 10:48 AM, Iain Buclaw wrote: >> Something this large can be integration tested on a svn/git branch, if you >> need others to help out. >> > > It would probably be easier for me to maintain also, rather than > continuously regenerating patches each time I make an update to > reflect something that changed in GCC. A branch doesn't remove the need to post patches for review; only eases the burden of working with external people before it hits trunk.
Re: [PATCH 9/13] D: D2 Testsuite Dejagnu files.
On 31 May 2017 at 01:32, Mike Stump wrote: > On May 28, 2017, at 2:16 PM, Iain Buclaw wrote: >> >> This patch adds D language support to the GCC test suite. > > Ok. If you could ensure that gcc without D retains all it's goodness and > that gcc with D works on 2 different systems, that will help ensure > integration smoothness. > > Something this large can be integration tested on a svn/git branch, if you > need others to help out. > It would probably be easier for me to maintain also, rather than continuously regenerating patches each time I make an update to reflect something that changed in GCC. Iain.
Re: [PATCH 9/13] D: D2 Testsuite Dejagnu files.
On 31 May 2017 at 11:11, Matthias Klose wrote: > On 30.05.2017 16:32, Mike Stump wrote: >> On May 28, 2017, at 2:16 PM, Iain Buclaw wrote: >>> >>> This patch adds D language support to the GCC test suite. >> >> Ok. If you could ensure that gcc without D retains all it's goodness and >> that gcc with D works on 2 different systems, that will help ensure >> integration smoothness. >> >> Something this large can be integration tested on a svn/git branch, if you >> need others to help out. > > I built the library (x86 and ARM32) and the D frontend on several Debian > architectures and OSes (Linux, KFreeBSD, Hurd) in the past, but can do that > with > the proposed patches again. A svn/git branch would be helpful for that, if a > recent test is required. > > Matthias Indeed, I have all cross-compilers running on explore.dgnu.org at least. A little hello world program should give a rough idea of which targets are supported by libphobos - x86/64, ARM/64, MIPS/64 and PPC/64 should be either supported or partial. And if partial, then I suspect that it's only because there's a missing 'CRuntime_xxx' version define in the gcc/config patches. Although I only use gdc on Linux myself, the reference D compiler is tested on x86/Linux, OSX, Solaris, and FreeBSD. I'll optimistically say we should work on these as well, although off the top of my head, the module dso support may need looking at in the library. Iain.
Re: [PATCH 9/13] D: D2 Testsuite Dejagnu files.
On 30.05.2017 16:32, Mike Stump wrote: > On May 28, 2017, at 2:16 PM, Iain Buclaw wrote: >> >> This patch adds D language support to the GCC test suite. > > Ok. If you could ensure that gcc without D retains all it's goodness and > that gcc with D works on 2 different systems, that will help ensure > integration smoothness. > > Something this large can be integration tested on a svn/git branch, if you > need others to help out. I built the library (x86 and ARM32) and the D frontend on several Debian architectures and OSes (Linux, KFreeBSD, Hurd) in the past, but can do that with the proposed patches again. A svn/git branch would be helpful for that, if a recent test is required. Matthias
Re: [PATCH 9/13] D: D2 Testsuite Dejagnu files.
On May 28, 2017, at 2:16 PM, Iain Buclaw wrote: > > This patch adds D language support to the GCC test suite. Ok. If you could ensure that gcc without D retains all it's goodness and that gcc with D works on 2 different systems, that will help ensure integration smoothness. Something this large can be integration tested on a svn/git branch, if you need others to help out.
