Displaying 3 results from an estimated 3 matches for "823c9b61".
2012 Dec 01
0
[LLVMdev] Use rand_r() instead of non-reentrant thread-unsafe rand() in GetRandomNumber()
If we're keeping the state locally now, perhaps we should store it in a
per-thread variable. I know rand() isn't thread safe to begin with, but it
seems like rand_r() can be since it should keep no external state.
On Sat, Dec 1, 2012 at 11:17 AM, Dmitry Mikushin <dmitry at kernelgen.org>wrote:
> Dear all,
>
> In our LLVM-based compiler pipeline a major part of code
2012 Dec 01
2
[LLVMdev] Use rand_r() instead of non-reentrant thread-unsafe rand() in GetRandomNumber()
Dear all,
In our LLVM-based compiler pipeline a major part of code generation is
taken into application runtime. One side-effect of this organization is a
need to be very careful about using code that might diverge application
state. And we found that simple generation of temporary files over LLVM
APIs introduces random noise into the program result. There reason is that
LLVM's
2012 Dec 01
2
[LLVMdev] Use rand_r() instead of non-reentrant thread-unsafe rand() in GetRandomNumber()
...du
>> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>>
>>
>
>
> --
>
> Thanks,
>
> Justin Holewinski
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20121201/823c9b61/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: llvm.rand.patch
Type: application/octet-stream
Size: 410 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20121201/823c9b61/attachment.obj>