[Issue 13938] IASM shouldn't be able to access TLS variables

https://issues.dlang.org/show_bug.cgi?id=13938 Vladimir Panteleev changed: What|Removed |Added CC||deadal...@gmail.com --- Comment #6 from

[Issue 13938] IASM shouldn't be able to access TLS variables

shouldn't be able to access TLS variables https://github.com/D-Programming-Language/dmd/commit/756cda4c5a73ac35c7f48faae20de73493d210a4 Merge pull request #4260 from 9rnsr/fix_iasm --

[Issue 13938] IASM shouldn't be able to access TLS variables

shouldn't be able to access TLS variables https://github.com/D-Programming-Language/dmd/commit/756cda4c5a73ac35c7f48faae20de73493d210a4 Merge pull request #4260 from 9rnsr/fix_iasm Issue 13938 & 13939 - Disallow non-trivial variable accesses in iasm --

[Issue 13938] IASM shouldn't be able to access TLS variables

https://issues.dlang.org/show_bug.cgi?id=13938 github-bugzi...@puremagic.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|-

[Issue 13938] IASM shouldn't be able to access TLS variables

https://issues.dlang.org/show_bug.cgi?id=13938 --- Comment #3 from Martin Nowak --- For example this is the sequence to write to a TLS variable in X86 code (non-PIC), the one for X64 doesn't work, because dmd's IASM doesn't support RIP relative addressing. size_t a; void main() { asm {

[Issue 13938] IASM shouldn't be able to access TLS variables

https://issues.dlang.org/show_bug.cgi?id=13938 --- Comment #2 from Martin Nowak --- It's fairly tricky, we would need to ensure that the correct code sequence is used. That's not really trackable and many can't be correctly written in D's IASM. So indeed it would be better to disallow them. --

[Issue 13938] IASM shouldn't be able to access TLS variables

https://issues.dlang.org/show_bug.cgi?id=13938 Kenji Hara changed: What|Removed |Added Keywords||accepts-invalid, pull --- Comment #1 from Kenji