similar to: Using std::chrono

VS2013 support is dropped in about 1 week from now :) On Thu, Oct 6, 2016 at 11:37 PM Mueller-Roemer, Johannes Sebastian < Johannes.Sebastian.Mueller-Roemer at igd.fraunhofer.de> wrote: > Visual Studio up to and including VS2013 implements > std::chrono::high_resolution_clock in an absolutely unusable manner (it is > a very low resolution clock…) [1]. Also, division is implemented

Hi, I want an efficient way to implement function pow in LLVM instead of invoking pow() math built-in. For algorithm part, I am clear for the logic. But I am not quite sure for which parts of LLVM should I replace built-in pow with another efficient pow implementation. Any comments and feedback are appreciated. Thanks! -- Wei Ding -------------- next part -------------- An HTML attachment was

On Aug 10, 2018, at 1:28 PM, Marshall Clow via cfe-dev <cfe-dev at lists.llvm.org> wrote: > > * The clock stuff being added in C++20 has already been discussed here. I’ve missed the discussions on file_time_type, however I thought I should throw in my opinion here before it is too late to do anything about it. I believe it is a mistake to model file_time_type with 128 bits. It

Sorry ... I missed mentioning the details - this is the error I get - root at no1slu398:~/Documents/LLVM/tmp# clang++ -std=c++0x hello.cpp In file included from hello.cpp:1: In file included from /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../../include/c++/4.6/thread:38: /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../../include/c++/4.6/chrono:535:6: error: no matching constructor for initialization of

Hi, I'd really appreciate some pointers in this regard. Regards, Kashyap On Wed, Oct 16, 2013 at 5:43 PM, C K Kashyap <ckkashyap at gmail.com> wrote: > Sorry ... I missed mentioning the details - > > this is the error I get - > > root at no1slu398:~/Documents/LLVM/tmp# clang++ -std=c++0x hello.cpp > In file included from hello.cpp:1: > In file included from >

All, I'm in the process of upgrading an LLVM client from using 3.8 to using 4.0 and am running into the following issue: // compile with: // clang++ -std=c++11 -Wno-c++14-extensions -S -emit-llvm // ~/chrono.cpp -o chrono.ll #include <chrono> #include <ratio> #include <thread> using namespace std; using namespace std::chrono; using tick = ratio<1, 300>; using

I dont know LTB or what it exact is, but Add in /etc/ldap/ldap.conf TLS_REQCERT allow Setup your own "rootCA" like this. ( if not done, apt-get install ca-certificates ) mkdir -p /usr/local/share/ca-certificates/chrono mv /etc/ssl/ca_chrono-dom.lan.pem /usr/local/share/ca-certificates/chrono update-ca-certificates ! MUST BE /usr/local/share/ca-certificates else its not picked up

Hello! You can now change the password for the User when even this expired password or "next logon"? PS: With the active account, was already working the password change. Hug. Em 11-05-2016 07:17, Charles-Henri Falconnet escreveu: > It works now for all my web apps ! > If you have a AC.pem, juste rename in AC.crt (update-ca-certificates > recognizes only crt files, man

We want to compute a pseudo R-squared for a model whose parameter estimation was based on maximum likelihood (function likfit, package geoR). I tried to compute the R2 proposed by Maddala (1983) which compare the maximized likelihood for the model without any predictor and the maximized likelihood for the model with all predictors. I got a really low value (0,01%). Did I miss something? Are

I'm not sure if I should bother you team with this, apologies in case it's a bother. I'm trying gcc 6.2.1 (from devtoolset-6) with R, everything seems to work just fine, except for mzR. Here is failed build: g++ -m64 -shared -L/usr/lib64/R/lib -Wl,-z,relro -o mzR.so cramp.o ramp_base64.o ramp.o RcppRamp.o RcppRampModule.o rnetCDF.o RcppPwiz.o RcppPwizModule.o RcppIdent.o

I generated maps with the function symbols (graphics). These are basic maps generated with : symbols(x,y,circles=myvariable) where x et y are spatial coordinates corresponding to replicates of "myvariable". I would associate legend to this kind of maps, is it possible? Regards, Marion. -- Marion Jacquot Laboratoire de Chrono-environnement UMR UFC/CNRS 6249 USC INRA Universit? de

Thank you. > On Jul 3, 2019, at 4:04 AM, Justin Clift <justin at postgresql.org> wrote: > > On 2019-07-01 00:22, Marty Itzkowitz via llvm-dev wrote: >> I also tried spack install llvm at develop on a POWER9 (ppc641e) >> machine, but I can not find a compiler that >> will compile it. gcc 4.8.5 is reported as too old, and gcc 7.3.0 and >> 8.1.0 both fail in

I do this on a vanilla-clean R installation, simply: > biocLite("mzR") it pulls some deps in which compile fine, only mzR fails. ... meanwhile... I grabbed devtools and comiled github master - still fails. Should I attach build log? One should not send attachments to the list.. I don't suppose? On 21/12/16 17:06, Martin Morgan wrote: > mzR is a Bioconductor package, so

Does it build with libstdc++? I've got this with fresh clang, -std=c++11: In file included from ../projects/lld/lib/ReaderWriter/ELF/./SectionChunks.h:19: In file included from ../projects/lld/include/lld/Core/Parallel.h:28: In file included from /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../../include/c++/4.6/condition_variable:38:

Hi, My current understanding of the problem (based on https://reviews.llvm.org/D49774) is that we have a type, file_time_type, which is part of the ABI and is currently defined as std::chrono::time_point<_FileSystemClock>, where _FileSystemClock is an internal type represented using a __int128_t. However, C++20 will add a type called file_clock and redefine file_time_type to be

Why did you want the symbols moved out of libc++experimental, and for the header to be moved from <experimental/filesystem> to <filesystem>? It certainly seems like it'd be safer and clearer to move them back to the old locations, but it's not clear to me if that'd be trading off something else of value. Was there some other greater purpose served by the change in

Now that I can build LLVM on Windows, I tried doing it. -------------------------- ... some good stuff ... C:/LLVM/llvm-project/llvm/lib/Support/Chrono.cpp:35:17: error: '::localtime_s' has not been declared; did you mean 'localtime'? 35 | int Error = ::localtime_s(&Storage, &OurTime); | ^~~~~~~~~~~ | localtime (The error

Hi Evgeniy, Can you add the step to checkout lld and build and run the unittests then ? Thanks Shankar Easwaran On 9/10/2013 4:59 AM, Evgeniy Stepanov wrote: > Does it build with libstdc++? I've got this with fresh clang, -std=c++11: > > In file included from ../projects/lld/lib/ReaderWriter/ELF/./SectionChunks.h:19: > In file included from

I saw an email about 8.0.1 being not quite out, and planning for 9.0.0. When is 8.0.1 supposed to come out? I installed llvm at develop on x86 on March 30, and its clang says it is version 9.0.0 (trunk 357348). I tried to do another spack install llvm at develop, but it said that I already had it installed. Does that mean there were no changes since March 30, or does spack not look for any

dovecot 2.1.1 I access my IMAP folders through SquirrelMail as a result of 'part copying' (probably through web client ? not sure), that is copying/moving some emails, later, the rest, I have a sub folder where I have maybe 30 emails from 2012 appear at the very end like so 2013/2012/2010/.../2006/2005/2012 how can I re-sort ? thanks Voytek