search for: cpp11

~~~ Not to be applied, for discussion only ~~~ I think we need some kind of "checkpatch" script to catch all the annoying, nitpicky code style issues that submitters trip up on. I looked at a few scripts that exist, primarily the ones from Linux and qemu (massive and complicated), and libvirt (small and sane). There are a couple of problems: (1) Linux/qemu-style checkpatch only

Hi Julian, > Some areas/ideas we are especially interested in: > Adaption of Clang to support OpenMP (http://clang-omp.github.io/), but haven't been able to contact one of the developers yet. This project is owned by my team, and we certainly welcome contributions! Have you tried to contact us via https://github.com/clang-omp/clang/issues ? Either way, it is really hard to find a

See previous version: https://www.redhat.com/archives/libguestfs/2016-April/msg00021.html The formatting in this second version isn't too bad. Still a few corner cases to sort out. Rich.

On 9/20/18 5:15 PM, Duncan Murdoch wrote: > On 20/09/2018 6:59 AM, Ralf Stubner wrote: >> It is difficult to do this in a package, since R does not provide access >> to the random bits generated by the RNG. Only a float in (0,1) is >> available via unif_rand(). > > I believe it is safe to multiply the unif_rand() value by 2^32, and take > the whole number part as an

Dear Clang/LLVM community! We (a group of 3 highly motivated CS grad students) are taking a class about compilers and optimizations. This class offers the option of doing a implementation project (instead of reading/writing x papers) for its main part. Of course hacking is much more fun than ... ;) So my question is do you know of any open points, compiler passes, optimizations in the LLVM /