<br><br><div class="gmail_quote">On 17 August 2010 05:47, Brad Roberts <span dir="ltr"><<a href="mailto:braddr@puremagic.com">braddr@puremagic.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">On 8/16/2010 9:33 PM, dsimcha wrote:<br>
> What are the current blockers to merging non-ancient versions of D2 into GDC?<br>
> I've been quietly following the project and noticed that:<br>
><br>
> 1. It's actively being worked on.<br>
><br>
> 2. D1 is up to date.<br>
><br>
> 3. There were a bunch of issues w.r.t. druntime, but these seem to be resolved.<br>
><br>
> 4. A new version of D2 hasn't been merged in ~1 month, even though the<br>
> project is generally active.<br>
><br>
> 5. There was some concern about breaking the currently working 2.019. IMHO<br>
> this is **completely** unwarranted, as support for such an outdated D2 version<br>
> is probably **completely useless** to just about everyone. Probably no<br>
> non-trivial code that compiles for 2.019 will work on the latest version or<br>
> vice-versa, and the only code that's still written for 2.019 is really old,<br>
> unmaintained code that noone cares about. IMHO until you're at least close to<br>
> the latest version, you should just break older versions with reckless abandon<br>
> to march towards getting recent, useful versions working.<br>
<br>
</div></div>Along similar lines, I'd dearly love to see gdc+d2 sitting on top of the<br>
druntime rather than maintaining an internal, ever drifting, fork. To that end,<br>
I'd welcome patches (preferably small baby-step type patches, not huge lump sum<br>
code drops) to narrow the differences.<br>
<br>
<br>
</blockquote></div><br>To be honest, currently it's been like writing the first chapter of a novel. I *will* get started on it ... right after I get X done first, and maybe check my email, because that it important too ( and can often consume a day ;)<div>
<br></div><div>Current developments that are taking priority first (in order) are:</div><div><br></div><div>* Updating/Uploading packages in Debian and Ubuntu - as of writing, package is currently being built in Debian, with a predicted success across all 14 supported architectures. >:-)</div>
<div>* Port GDC to GCC-4.4 - nearly done, with one or two show-stoppers remaining with static chain decls and exprs.</div><div>* Sort out the outstanding merges of D 1.062 and 1.063 - which somewhere along the line lost 64bit support. !!! - barely even started looking into it yet.</div>
<div><br></div><div><br></div><div>Current blockers that need to be organised out (in my opinion) before D2 can be emerged are:</div><div><br></div><div>* Integration into current GCC patches, which will require a regeneration of _all_ patches in the patch directory (even those I cannot account for as working).</div>
<div>* Figuring out what internals need to be migrated from the current phobos2 directory, what needs to keep.</div><div>* A general consensus needs to be reached on how we should handle ASM version specifiers. Gnu_InlineAsmX86? D_InlineAsmX86? 64bit? Sort out calling conventions?</div>
<div>* GDC Driver updates to tie the whole thing together - the easy bit. ;-)</div><div><br></div><div>Anything I missed? Should I be pushing D2 further up the stack of my list of TODOs?</div><div><br></div><div>Regards</div>
<div><div><div><br>-- <br>Iain Buclaw<br><br>*(p < e ? p++ : p) = (c & 0x0f) + '0';<br>
</div></div></div>