Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

testptrref: fix finding TLS range #9341

Merged
merged 1 commit into from
Feb 10, 2019
Merged

Conversation

rainers
Copy link
Member

@rainers rainers commented Feb 9, 2019

Not sure why this test didn't fail for me or on Appveyor, but it does now (probably after an update to the VC toolchain). As noted in dlang/druntime#1910: With VS2017 15.3.1 segment .tls is no longer written to a separate image section, so _tls_start and _tls_end no longer happen to work as both __gshared and TLS section offsets.

This now uses the TLS detection from druntime.

@wilzbach
Copy link
Member

wilzbach commented Feb 9, 2019

Not sure why this test didn't fail for me or on Appveyor, but it does now

BTW partially OT, but if we ever want to add more Windows jobs, run into problems with AppVeyor or simply overclog the queue with AppVeyor (we only have one free job there), Azure CI pipelines might be an option. As an open-source project, one gets 10 parallel jobs for free:

https://azure.microsoft.com/en-us/services/devops/pipelines/

I saw that the LDC people are testing this out too at the moment:

ldc-developers/ldc#2998

@WalterBright WalterBright merged commit 77068b9 into dlang:master Feb 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants