www.digitalmars.com         C & C++   DMDScript  

digitalmars.D - Bug 8859: Solaris port of the toolchain questions

--001a11c139bae03b0704fc3b31f5
Content-Type: text/plain; charset=UTF-8

So I've been working on Bug 8859 (really on Illumos which is the fork of
the source that remained open after Oracle bought Sun, though for X86,
they're still similar enough that this should for now work on either).

To date, I've been doing my work with GDC (DMD was generating objects with
some invalid ELF sections, so I figured I'd come back to that when I have
more alcohol handy to put on my linker alien hat).

After a few evenings of work, I've managed to get GDC to produce working
binaries and to pass all the Druntime unit tests.  I'm still working on
getting the  Phobos unit tests to pass, so it's not 100% ready yet.

I have a couple of questions:

1. As there was a decent amount of added code (and a few fixes of the
existing bits of Solaris support), would it be preferred to file individual
bugs for each issue, or just put it all under 8859 once it's all working?

2. I noticed a lot of declarations that are identical and duplicated for
all the *ix platforms, even when they are implementing a standard of some
sort (e.g. the AF_ values are IANA assigned, one should expect them to have
the same value everywhere, just perhaps some platforms perhaps not always
having the latest list).

Is the rationale to just match the corresponding system's .h files as close
as possible vs. a more consolidated version using version blocks to contain
the variation or implementation-defined portions?

--001a11c139bae03b0704fc3b31f5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">So I&#39;ve been working on Bug 8859 (really on Illumos wh=
ich is the fork of the source that remained open after Oracle bought Sun, t=
hough for X86, they&#39;re still similar enough that this should for now wo=
rk on either).<div>
<br></div><div>To date, I&#39;ve been doing my work with GDC (DMD was gener=
ating objects with some invalid ELF sections, so I figured I&#39;d come bac=
k to that when I have more alcohol handy to put on my linker alien hat).</d=
iv>
<div><br></div><div>After a few evenings of work, I&#39;ve managed to get G=
DC to produce working binaries and to pass all the Druntime unit tests. =C2=
=A0I&#39;m still working on getting the =C2=A0Phobos unit tests to pass, so=
 it&#39;s not 100% ready yet.</div>
<div><br></div><div>I have a couple of questions:</div><div><br></div><div>=
1. As there was a decent amount of added code (and a few fixes of the exist=
ing bits of Solaris support), would it be preferred to file individual bugs=
 for each issue, or just put it all under 8859 once it&#39;s all working?</=
div>
<div><br></div><div>2. I noticed a lot of declarations that are identical a=
nd duplicated for all the *ix platforms, even when they are implementing a =
standard of some sort (e.g. the AF_ values are IANA assigned, one should ex=
pect them to have the same value everywhere, just perhaps some platforms pe=
rhaps not always having the latest list).</div>
<div><br></div><div>Is the rationale to just match the corresponding system=
&#39;s .h files as close as possible vs. a more consolidated version using =
version blocks to contain the variation or implementation-defined portions?=
</div>
<div><br></div></div>

--001a11c139bae03b0704fc3b31f5--
Jun 19 2014