On 2016-01-11 23:44, bitwise wrote:
So..I've only had time to glance at the code, but it looks like you've
effectively moved this issue out of the way of shared libraries
entirely, and that no interaction between shared libs and TLS is needed
at all..is this correct?
Yes, I think so. I
On 1/12/2016 12:36 PM, Andrei Alexandrescu wrote:
On 01/12/2016 03:30 PM, Jacob Carlborg wrote:
On 2016-01-12 17:48, Walter Bright wrote:
From reading the responses here, I believe the best solution is to
continue to support OSX 32 bit, but as legacy support. This means
folding in changes to
On 2016-01-12 17:48, Walter Bright wrote:
From reading the responses here, I believe the best solution is to
continue to support OSX 32 bit, but as legacy support. This means
folding in changes to the 64 bit support, but not adding features if
they are not a natural consequence of the 64 bit
On 01/12/2016 03:30 PM, Jacob Carlborg wrote:
On 2016-01-12 17:48, Walter Bright wrote:
From reading the responses here, I believe the best solution is to
continue to support OSX 32 bit, but as legacy support. This means
folding in changes to the 64 bit support, but not adding features if
On Tuesday, 12 January 2016 at 21:28:43 UTC, Walter Bright wrote:
On 1/12/2016 12:36 PM, Andrei Alexandrescu wrote:
On 01/12/2016 03:30 PM, Jacob Carlborg wrote:
On 2016-01-12 17:48, Walter Bright wrote:
From reading the responses here, I believe the best
solution is to
continue to support
On 1/12/2016 2:20 PM, bitwise wrote:
On Tuesday, 12 January 2016 at 21:28:43 UTC, Walter Bright wrote:
On 1/12/2016 12:36 PM, Andrei Alexandrescu wrote:
On 01/12/2016 03:30 PM, Jacob Carlborg wrote:
On 2016-01-12 17:48, Walter Bright wrote:
From reading the responses here, I believe the
On 1/10/2016 9:12 AM, Jacob Carlborg wrote:
I've implemented native TLS in DMD on OS X for 64bit. Now the question is, does
it need to work for 32bit as well?
The easiest would be to drop the 32bit support all together. Other options would
be to continue to use emulate TLS on 32bit or implement
On Monday, 11 January 2016 at 07:40:37 UTC, Jacob Carlborg wrote:
On 2016-01-10 21:58, bitwise wrote:
Awesome!
Is there a way I can have a look at the code? I'd like to
start looking
into how this will fit together with shared library support.
On Monday, 11 January 2016 at 07:44:18 UTC, Jacob Carlborg wrote:
I doesn't solve the problem but it's a prerequisite for solving
dynamic libraries. That's why I started working on this :)
Great!
On Sunday, 10 January 2016 at 17:12:40 UTC, Jacob Carlborg wrote:
I've implemented native TLS in DMD on OS X for 64bit. Now the
question is, does it need to work for 32bit as well?
The easiest would be to drop the 32bit support all together.
Other options would be to continue to use emulate
On 2016-01-10 21:58, bitwise wrote:
Awesome!
Is there a way I can have a look at the code? I'd like to start looking
into how this will fit together with shared library support.
https://github.com/D-Programming-Language/dmd/pull/5346
--
/Jacob Carlborg
On 2016-01-10 23:15, Guillaume Piolat wrote:
I'm using 32-bit support of DMD and I would strongly prefer if it wasn't
removed. At least staying the same as today.
The problem is that I don't control what bitness users want, because of
network effects some users still use 32-bit software. Every
On Sunday, 10 January 2016 at 17:12:40 UTC, Jacob Carlborg wrote:
The easiest would be to drop the 32bit support all together.
Other options would be to continue to use emulate TLS on 32bit
or implement native TLS for 32bit as well. I would prefer to
not have to do this for 32bit as well.
I
I've implemented native TLS in DMD on OS X for 64bit. Now the question
is, does it need to work for 32bit as well?
The easiest would be to drop the 32bit support all together. Other
options would be to continue to use emulate TLS on 32bit or implement
native TLS for 32bit as well. I would
On Sunday, 10 January 2016 at 17:12:40 UTC, Jacob Carlborg wrote:
I've implemented native TLS in DMD on OS X for 64bit. Now the
question is, does it need to work for 32bit as well?
The easiest would be to drop the 32bit support all together.
Other options would be to continue to use emulate
On 2016-01-10 20:42, John Colvin wrote:
I definitely don't care about 32 bit on OS X. However, I see no need to
drop it if the current TLS emulation works.
It's easier to remove it than supporting both :)
--
/Jacob Carlborg
On Sunday, 10 January 2016 at 17:12:40 UTC, Jacob Carlborg wrote:
I've implemented native TLS in DMD on OS X for 64bit. Now the
question is, does it need to work for 32bit as well?
The easiest would be to drop the 32bit support all together.
Other options would be to continue to use emulate
On Sunday, 10 January 2016 at 18:06:11 UTC, Jack Stouffer wrote:
Mountain Lion, which was released in 2012, was the last version
to ship a 32bit version.
But 32-bit programs still work on latest OSX, and are sometimes
needed.
On Sunday, 10 January 2016 at 17:12:40 UTC, Jacob Carlborg wrote:
I've implemented native TLS in DMD on OS X for 64bit. Now the
question is, does it need to work for 32bit as well?
The easiest would be to drop the 32bit support all together.
Other options would be to continue to use emulate
19 matches
Mail list logo
