Commit 44f2687d authored by Niels Möller's avatar Niels Möller
Browse files

Explain why x86_64 fat initialization doesn't need any memory barrier.

parent 29d6dacf
...@@ -150,10 +150,10 @@ fat_init (void) ...@@ -150,10 +150,10 @@ fat_init (void)
_aes_encrypt_vec = _nettle_aes_encrypt_x86_64; _aes_encrypt_vec = _nettle_aes_encrypt_x86_64;
_aes_decrypt_vec = _nettle_aes_decrypt_x86_64; _aes_decrypt_vec = _nettle_aes_decrypt_x86_64;
} }
/* FIXME: We ought to use some thread-aware memory barrier before
setting the initialized flag. For now, just do another cpuinfo /* The x86_64 architecture should always make stores visible in the
call to get some synchronization. */ right order to other processors (except for non-temporal stores
_nettle_cpuid (1, cpuid_data); and the like). So we don't need any memory barrier. */
initialized = 1; initialized = 1;
} }
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment