Re: [libphobos] Work around lack of dlpi_tls_modid before Solaris 11.5

2019-04-14 Thread Rainer Orth
Hi Iain, > On Tue, 9 Apr 2019 at 21:27, Rainer Orth > wrote: >> >> Rainer Orth writes: >> >> > Before Solaris 11.5, struct dl_phdr_info lacked the dlpi_tls_modid >> > member. While the support might be backported to Solaris 11.4, it >> > certainly won't to previous Solaris releases. To work a

Re: [libphobos] Work around lack of dlpi_tls_modid before Solaris 11.5

2019-04-13 Thread Iain Buclaw
On Tue, 9 Apr 2019 at 21:27, Rainer Orth wrote: > > Rainer Orth writes: > > > Before Solaris 11.5, struct dl_phdr_info lacked the dlpi_tls_modid > > member. While the support might be backported to Solaris 11.4, it > > certainly won't to previous Solaris releases. To work around this, I've > >

Re: [libphobos] Work around lack of dlpi_tls_modid before Solaris 11.5

2019-04-09 Thread Rainer Orth
Rainer Orth writes: > Before Solaris 11.5, struct dl_phdr_info lacked the dlpi_tls_modid > member. While the support might be backported to Solaris 11.4, it > certainly won't to previous Solaris releases. To work around this, I've > used the following patch. Again, it's pretty straightforward.

Re: [libphobos] Work around lack of dlpi_tls_modid before Solaris 11.5

2019-02-04 Thread Rainer Orth
Hi Johannes, >> I suspect the two testsuite regressions (compared to a build with >> dlpi_tls_modid present) I mentioned are exactly of the kind you mention: >> >> e.g. the gdc.test/runnable/testaa.d failures are like this >> >> core.exception.rangeer...@gdc.test/runnable/testaa.d(410): Range viol

Re: [libphobos] Work around lack of dlpi_tls_modid before Solaris 11.5

2019-02-02 Thread Johannes Pfau
Hi Rainer, I suspect the two testsuite regressions (compared to a build with dlpi_tls_modid present) I mentioned are exactly of the kind you mention: e.g. the gdc.test/runnable/testaa.d failures are like this core.exception.rangeer...@gdc.test/runnable/testaa.d(410): Range violation -

Re: [libphobos] Work around lack of dlpi_tls_modid before Solaris 11.5

2019-02-01 Thread Rainer Orth
Hi Johannes, > I'd recommend not using such a workaround: > > This means getTLSRange will always return an empty range, but the GC uses > this to scan TLS memory. This means a GC collection can delete objects > which are still pointed to from TLS. This leads to hard to debug errors, > and if I rem

Re: [libphobos] Work around lack of dlpi_tls_modid before Solaris 11.5

2019-01-31 Thread Johannes Pfau
Hi Rainer, I'd recommend not using such a workaround: This means getTLSRange will always return an empty range, but the GC uses this to scan TLS memory. This means a GC collection can delete objects which are still pointed to from TLS. This leads to hard to debug errors, and if I remember cor