December 22
On 12/21/2017 5:30 AM, David Nadlinger wrote:
> Just to clarify, that's true for for DMD only – TLS should work just fine on macOS with LDC.

Is there a bugzilla issue with just what is wrong with the TLS code generation on macOS?
December 23
On 2017-12-23 00:18, Walter Bright wrote:

> Is there a bugzilla issue with just what is wrong with the TLS code generation on macOS?

There's nothing wrong with TLS on macOS. It's just that there are additional work that needs to be done. Just the same as TLS worked before dynamic libraries worked on Linux.

-- 
/Jacob Carlborg
December 23
On Thursday, 21 December 2017 at 13:44:18 UTC, Benjamin Thaut wrote:
> Ideally we should end up with visibility hidden being the default and only making symbols visible which use "export", because that is what it was designed for in the first place.

Yes, that's the long-term goal.
December 23
On 12/23/2017 6:26 AM, Jacob Carlborg wrote:
> On 2017-12-23 00:18, Walter Bright wrote:
> 
>> Is there a bugzilla issue with just what is wrong with the TLS code generation on macOS?
> 
> There's nothing wrong with TLS on macOS. It's just that there are additional work that needs to be done. Just the same as TLS worked before dynamic libraries worked on Linux.

It'd be nice to collect information on what needs to be done and file a bugzilla issue on it. Otherwise it's just generic "doesn't work on macOS" which contains no useful information.
December 25
On 2017-12-23 21:59, Walter Bright wrote:

> It'd be nice to collect information on what needs to be done and file a
> bugzilla issue on it. Otherwise it's just generic "doesn't work on
> macOS" which contains no useful information.

If I knew exactly what would need to be done I would most likely have done it already :). Perhaps Martin that implemented the support on Linux or David that, I think, implemented it for LDC on macOS would be better suited for such a bugzilla issue.

-- 
/Jacob Carlborg
December 27
On Monday, 25 December 2017 at 08:57:09 UTC, Jacob Carlborg wrote:
> If I knew exactly what would need to be done I would most likely have done it already :). Perhaps Martin that implemented the support on Linux or David that, I think, implemented it for LDC on macOS would be better suited for such a bugzilla issue.

If you know that it doesn't work, please file an issue; a bug that just says "this doesn't work" is more valuable than its absence.

If you have a test case, that is valuable; "what would need to be done" is to make the test case work.

If you know that it works with LDC, that is also valuable; "what would need to be done" is to port over LDC's fixes.

I haven't used a Mac since 2012 (an experience that I am anxious to avoid repeating), so I don't even know whether TLS works with dynamic libraries on OSX. I can't test fixes. All I could do is report that there's a rumor.
Next ›   Last »
1 2