Thanks for confirming Ian, this is very helpful. I agree with the
implication that hacking Go on x86 to avoid TLS would not be a productive
use of time compared to adding TLS support to the operating system.
Thanks again.
On Sat, Aug 1, 2020 at 6:27 PM Ian Lance Taylor wrote:
> On Sat, Aug 1, 2
On Sat, Aug 1, 2020 at 2:46 PM wrote:
>
> You're right - after re-reading this I realize I could have been more
> specific.
>
> I am working with a custom OS kernel that supports a subset of Linux
> syscalls. However, it does not support TLS, which on i386 I believe typically
> requires OS supp
Hi Jan,
You're right - after re-reading this I realize I could have been more
specific.
I am working with a custom OS kernel that supports a subset of Linux
syscalls. However, it does not support TLS, which on i386 I believe
typically requires OS support to set up and restore the GDT and %gs s
Not sure I understand correctly, but TLS is usually provided on some level
by the kernel of the specific OS. Another level is TLS as in, for example
pthreads.
The Go runtime probably uses one or the other additionally to goroutine
local storage.
Can you please clarify?
On Sat, Aug 1, 2020, 20:08
Hi all,
Is it possible to build pure Go (no cgo) programs targeting i386 without
TLS support? From reviewing the compiler flags and the compiler build
options it looks like this isn't possible, but I am hoping someone with
knowledge on the matter can comment definitively.
Thanks,
Evan
--
You
