Thread overview | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
January 24, 2015 2.066 announce? | ||||
---|---|---|---|---|
| ||||
Attachments: | i see that 2.066.1 is landed in GDC (heh, that was sudden! had to fix almost all my private patches...). is it still in testing stage, or it's already fully usable? and if it's usable, i believe that it worth announcing in "D.announce" NG. |
January 24, 2015 Re: 2.066 announce? | ||||
---|---|---|---|---|
| ||||
Posted in reply to ketmar | Am Sat, 24 Jan 2015 06:32:57 +0000 (UTC)
schrieb ketmar <ketmar@ketmar.no-ip.org>:
> i see that 2.066.1 is landed in GDC (heh, that was sudden! had to fix almost all my private patches...). is it still in testing stage, or it's already fully usable? and if it's usable, i believe that it worth announcing in "D.announce" NG.
I'd say testing stage. I'm still reducing one ARM codegen bug ;-)
|
January 24, 2015 Re: 2.066 announce? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Johannes Pfau Attachments:
| On 24 Jan 2015 08:40, "Johannes Pfau via D.gnu" <d.gnu@puremagic.com> wrote:
>
> Am Sat, 24 Jan 2015 06:32:57 +0000 (UTC)
> schrieb ketmar <ketmar@ketmar.no-ip.org>:
>
> > i see that 2.066.1 is landed in GDC (heh, that was sudden! had to fix almost all my private patches...). is it still in testing stage, or it's already fully usable? and if it's usable, i believe that it worth announcing in "D.announce" NG.
>
> I'd say testing stage. I'm still reducing one ARM codegen bug ;-)
Agreed. I'd say it's only released when it hits branch. Now it's in master, it allows people to test out their projects with it.
I also need to write up a formal changelog of what's gone in, what hasn't, and what has been backported from 2.067.
Iain.
|
January 24, 2015 Re: 2.066 announce? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Iain Buclaw | On Saturday, 24 January 2015 at 08:47:33 UTC, Iain Buclaw via D.gnu wrote:
> On 24 Jan 2015 08:40, "Johannes Pfau via D.gnu" <d.gnu@puremagic.com> wrote:
>>
>> Am Sat, 24 Jan 2015 06:32:57 +0000 (UTC)
>> schrieb ketmar <ketmar@ketmar.no-ip.org>:
>>
>> > i see that 2.066.1 is landed in GDC (heh, that was sudden! had to fix
>> > almost all my private patches...). is it still in testing stage, or
>> > it's already fully usable? and if it's usable, i believe that it
>> > worth announcing in "D.announce" NG.
>>
>> I'd say testing stage. I'm still reducing one ARM codegen bug ;-)
>
> Agreed. I'd say it's only released when it hits branch. Now it's in
> master, it allows people to test out their projects with it.
>
> I also need to write up a formal changelog of what's gone in, what hasn't,
> and what has been backported from 2.067.
>
> Iain.
I'm very much looking forward to this release: my code depends heavily on the 2.066 multidimensional array syntax and I'm eager to find out if GDC can give me some extra performance.
As for testing the current state of GDC: is there a way to cleanly add this testing stage version to my build matrix on Travis CI, e.g. is a binary available somewhere?
Stefan
|
January 24, 2015 Re: 2.066 announce? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Iain Buclaw Attachments: | On Sat, 24 Jan 2015 08:47:25 +0000, Iain Buclaw via D.gnu wrote:
> On 24 Jan 2015 08:40, "Johannes Pfau via D.gnu" <d.gnu@puremagic.com> wrote:
>>
>> Am Sat, 24 Jan 2015 06:32:57 +0000 (UTC)
>> schrieb ketmar <ketmar@ketmar.no-ip.org>:
>>
>> > i see that 2.066.1 is landed in GDC (heh, that was sudden! had to fix almost all my private patches...). is it still in testing stage, or it's already fully usable? and if it's usable, i believe that it worth announcing in "D.announce" NG.
>>
>> I'd say testing stage. I'm still reducing one ARM codegen bug ;-)
>
> Agreed. I'd say it's only released when it hits branch. Now it's in master, it allows people to test out their projects with it.
but it is in branch! ;-) i'm building my compiler from 'gdc-4.9' branch, and it answers "2066L" on `pragma(msg, __VERSION__);`. that was the reason for my question in the first place.
p.s. please, don't revert it! ;-)
|
January 24, 2015 Re: 2.066 announce? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Stefan Frijters Attachments:
| On 24 Jan 2015 10:20, "Stefan Frijters via D.gnu" <d.gnu@puremagic.com> wrote: > > On Saturday, 24 January 2015 at 08:47:33 UTC, Iain Buclaw via D.gnu wrote: >> >> On 24 Jan 2015 08:40, "Johannes Pfau via D.gnu" <d.gnu@puremagic.com> wrote: >>> >>> >>> Am Sat, 24 Jan 2015 06:32:57 +0000 (UTC) >>> schrieb ketmar <ketmar@ketmar.no-ip.org>: >>> >>> > i see that 2.066.1 is landed in GDC (heh, that was sudden! > had to fix >>> > almost all my private patches...). is it still in testing > stage, or it's already fully usable? and if it's usable, i believe > that it worth announcing in "D.announce" NG. >>> >>> I'd say testing stage. I'm still reducing one ARM codegen bug ;-) >> >> >> Agreed. I'd say it's only released when it hits branch. Now it's in master, it allows people to test out their projects with it. >> >> I also need to write up a formal changelog of what's gone in, what hasn't, >> and what has been backported from 2.067. >> >> Iain. > > > I'm very much looking forward to this release: my code depends heavily on the 2.066 multidimensional array syntax and I'm eager to find out if GDC can give me some extra performance. > As for testing the current state of GDC: is there a way to cleanly add this testing stage version to my build matrix on Travis CI, e.g. is a binary available somewhere? > > Stefan I will be updating docker images this weekend. https://github.com/ibuclaw/docker-gdc |
January 24, 2015 Re: 2.066 announce? | ||||
---|---|---|---|---|
| ||||
Posted in reply to ketmar | On 24 January 2015 at 11:08, ketmar via D.gnu <d.gnu@puremagic.com> wrote:
> On Sat, 24 Jan 2015 08:47:25 +0000, Iain Buclaw via D.gnu wrote:
>
>> On 24 Jan 2015 08:40, "Johannes Pfau via D.gnu" <d.gnu@puremagic.com> wrote:
>>>
>>> Am Sat, 24 Jan 2015 06:32:57 +0000 (UTC)
>>> schrieb ketmar <ketmar@ketmar.no-ip.org>:
>>>
>>> > i see that 2.066.1 is landed in GDC (heh, that was sudden! had to fix almost all my private patches...). is it still in testing stage, or it's already fully usable? and if it's usable, i believe that it worth announcing in "D.announce" NG.
>>>
>>> I'd say testing stage. I'm still reducing one ARM codegen bug ;-)
>>
>> Agreed. I'd say it's only released when it hits branch. Now it's in master, it allows people to test out their projects with it.
>
> but it is in branch! ;-) i'm building my compiler from 'gdc-4.9' branch, and it answers "2066L" on `pragma(msg, __VERSION__);`. that was the reason for my question in the first place.
>
> p.s. please, don't revert it! ;-)
No one told me this. :o)
Iain.
|
January 24, 2015 Re: 2.066 announce? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Iain Buclaw | Am Sat, 24 Jan 2015 11:56:31 +0000
schrieb "Iain Buclaw via D.gnu" <d.gnu@puremagic.com>:
> On 24 January 2015 at 11:08, ketmar via D.gnu <d.gnu@puremagic.com> wrote:
> > On Sat, 24 Jan 2015 08:47:25 +0000, Iain Buclaw via D.gnu wrote:
> >
> >> On 24 Jan 2015 08:40, "Johannes Pfau via D.gnu" <d.gnu@puremagic.com> wrote:
> >>>
> >>> Am Sat, 24 Jan 2015 06:32:57 +0000 (UTC)
> >>> schrieb ketmar <ketmar@ketmar.no-ip.org>:
> >>>
> >>> > i see that 2.066.1 is landed in GDC (heh, that was sudden! had to fix almost all my private patches...). is it still in testing stage, or it's already fully usable? and if it's usable, i believe that it worth announcing in "D.announce" NG.
> >>>
> >>> I'd say testing stage. I'm still reducing one ARM codegen bug ;-)
> >>
> >> Agreed. I'd say it's only released when it hits branch. Now it's in master, it allows people to test out their projects with it.
> >
> > but it is in branch! ;-) i'm building my compiler from 'gdc-4.9' branch, and it answers "2066L" on `pragma(msg, __VERSION__);`. that was the reason for my question in the first place.
> >
> > p.s. please, don't revert it! ;-)
>
>
> No one told me this. :o)
>
> Iain.
Sorry, I already updated the branches as I needed a 4.9.2 backport for testing. I should probably think twice about this next time :-)
|
January 24, 2015 Re: 2.066 announce? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Johannes Pfau Attachments: | On Sat, 24 Jan 2015 13:33:50 +0100, Johannes Pfau wrote:
> Sorry, I already updated the branches as I needed a 4.9.2 backport for testing. I should probably think twice about this next time :-)
i think that it was the right move. this way people who are using gcc 4.9 (me ;-) can test it too. not that i'm doing compiler unittests or so, but i'm working on my project with gdc, so there is a small chance to catch some bugs anyway.
|
January 24, 2015 Re: 2.066 announce? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Johannes Pfau | On 24 January 2015 at 12:33, Johannes Pfau via D.gnu <d.gnu@puremagic.com> wrote:
> Am Sat, 24 Jan 2015 11:56:31 +0000
> schrieb "Iain Buclaw via D.gnu" <d.gnu@puremagic.com>:
>
>> On 24 January 2015 at 11:08, ketmar via D.gnu <d.gnu@puremagic.com> wrote:
>> > On Sat, 24 Jan 2015 08:47:25 +0000, Iain Buclaw via D.gnu wrote:
>> >
>> >> On 24 Jan 2015 08:40, "Johannes Pfau via D.gnu" <d.gnu@puremagic.com> wrote:
>> >>>
>> >>> Am Sat, 24 Jan 2015 06:32:57 +0000 (UTC)
>> >>> schrieb ketmar <ketmar@ketmar.no-ip.org>:
>> >>>
>> >>> > i see that 2.066.1 is landed in GDC (heh, that was sudden! had to fix almost all my private patches...). is it still in testing stage, or it's already fully usable? and if it's usable, i believe that it worth announcing in "D.announce" NG.
>> >>>
>> >>> I'd say testing stage. I'm still reducing one ARM codegen bug ;-)
>> >>
>> >> Agreed. I'd say it's only released when it hits branch. Now it's in master, it allows people to test out their projects with it.
>> >
>> > but it is in branch! ;-) i'm building my compiler from 'gdc-4.9' branch, and it answers "2066L" on `pragma(msg, __VERSION__);`. that was the reason for my question in the first place.
>> >
>> > p.s. please, don't revert it! ;-)
>>
>>
>> No one told me this. :o)
>>
>> Iain.
>
> Sorry, I already updated the branches as I needed a 4.9.2 backport for testing. I should probably think twice about this next time :-)
Nah - I shouldn't have to have my finger dipped in everything. It's just given me a list of more things to update today.
Iain
|
Copyright © 1999-2021 by the D Language Foundation