similar to: [LLVMdev] change program names (configure --program-prefix=xxx)

Hello, I have a compiler in LLVM 2.9 for the KCPM3 processor. I'd like to create a subtarget for the new cpu version called KCPSM6. Besides a couple of new instructions which are not important at the moment, the KCPSM6 cpu has different instruction opcodes. Semantically the instructions are the same, hence I'd like to keep all the lowering and pattern matching stuff unmodified For

Hello, I am developing compiler for the 8-bit PicoBlaze processor in LLVM 2.9. The problem at hand is that the stack spilling code in this architecture modifies the machine FLAGS register (i.e. globally visible state). The LLVM core code does not know about this 'feature' and happily inserts spilling code anywhere it wants, thus (potentially) corrupting live FLAGS. Practically, the FLAGS

Adding --program-prefix support to the autoconf build has been an adventure. A patch was applied. It worked on the usual llvm bots, but failed on other bots with different configure options. The patch was reverted as it broke on bots specifying --build, --host, and --target in configure. An option is proposed here to change the behavior of program-prefix to it's normal behavior when

>> Can I tell tablegen to have two encodings and switch between them >> using a predicate? After some deliberations, I modified tablegen to generate several versions of the GenCodeEmitter file. My tablegen now accepts a new command line parameter called "emitter-instfld". This specifies the name of the field in Instruction that holds the encoded bytes. In my target's td

Dears, I have tested SVN on samba drive and it totally fails. Please help me to navigate in source code, where attributes are set. It would be better either to fix it or at least to block R attribute to set. fojtik@dvouramenna:~/ESC_sro/Kancl/.svn$ chmod 777 entries fojtik@dvouramenna:~/ESC_sro/Kancl/.svn$ ls -la entries -rwxrwxrwx 1 fojtik users 300 Mar 7 13:38 entries

What is the output of your logfile when you try to ping a public ip? Besides, you should change your internal ip addresses to private addresses (rfc 1918): 10.0.0.0 - 10.255.255.255 (10/8 prefix) 172.16.0.0 - 172.31.255.255 (172.16/12 prefix) 192.168.0.0 - 192.168.255.255 (192.168/16 prefix) best regards, Kenneth. -----Opprinnelig melding----- Fra: Marta

Hi Michael, I am wondering about the meaning of the cmake flags LLVM_ENABLE_LIBCXX and > LLVM_ENABLE_LIBCXXABI. Are they used to indicate that if the C/C++ compiler > for building LLVM is clang, and if this clang has support for libc++ with > libc++Abi, that both lib++ and libc++abi should be used (instead of linking > to the default, which at least on Linux is libstdc++)? Yes that

Also please note that there is a description of each option in the CMakeLists.txt :) llvm/trunk/CMakeLists.txt option(LLVM_ENABLE_MODULES "Compile with C++ modules enabled." OFF) option(LLVM_ENABLE_CXX1Y "Compile with C++1y enabled." OFF) option(LLVM_ENABLE_LIBCXX "Use libc++ if available." OFF) option(LLVM_ENABLE_LIBCXXABI "Use libc++abi when using

On 6/16/15 1:09 AM, Nick Lewycky wrote: > Anirudh Sivaraman wrote: >> On Mon, Jun 15, 2015 at 10:50 AM, mats >> petersson<mats at planetcatfish.com> wrote: >>> It will iterate over the instructions in the order that they are >>> stored in >>> the module/function/basicblock that they belong to. And that SHOULD, >>> assuming llvm-dis does

> /usr/local/libexec/gcc/x86_64-unknown-linux-gnu/4.2.1/ > -rwxr-xr-x 1 root root 25179621 2009-03-25 09:15 cc1 > -rwxr-xr-x 1 root root 27917074 2009-03-25 09:15 cc1plus > -rwxr-xr-x 1 root root 359307 2009-03-25 09:15 collect2 > drwxr-xr-x 2 root root 4096 2009-03-25 09:15 install-tools > > No llvm-prefix. That's correct and not a llvm-gcc problem. This is how

Hello everybody, So I am having some problems with llvm. When I've tried a lot of times to run and re-install the llvm, but the same error appears, so: esbox at embedded2i:~/llvm/projects/teste$ llvm-gcc hello.c -o hello esbox at embedded2i:~/llvm/projects/teste$ ls hello hello.c esbox at embedded2i:~/llvm/projects/teste$ ./hello Hello World esbox at

Hi everybody. I'm using BFAST program and I have some data to be analized (named "META.csv" for example). When I call BFAST in the following way: meta <- read.csv("C:/META.csv") meta.ts<-ts(meta, frequency=12, start = c(2005,9)) dis<-frequency(meta.ts) / length(meta.ts) meta.sc<-bfast(meta.ts, h=dis, max.iter=1) meta.sc$output The last statement has the

Dear current (and future) users of the "frontier" package, We are approaching the first stable version (1.0) of the frontier package, which provides tools for microeconomic Stochastic Frontier Analysis (SFA). I have uploaded a kind of beta release (version 0.99) of this package to CRAN. The most important differences to version 0.9 affect the user interface. I have modified the

Dear current (and future) users of the "frontier" package, We are approaching the first stable version (1.0) of the frontier package, which provides tools for microeconomic Stochastic Frontier Analysis (SFA). I have uploaded a kind of beta release (version 0.99) of this package to CRAN. The most important differences to version 0.9 affect the user interface. I have modified the

Hi, I am wondering about the meaning of the cmake flags LLVM_ENABLE_LIBCXX and LLVM_ENABLE_LIBCXXABI. Are they used to indicate that if the C/C++ compiler for building LLVM is clang, and if this clang has support for libc++ with libc++Abi, that both lib++ and libc++abi should be used (instead of linking to the default, which at least on Linux is libstdc++)? If not, what is the canonical way of

On Mon, Jun 15, 2015 at 10:50 AM, mats petersson <mats at planetcatfish.com> wrote: > It will iterate over the instructions in the order that they are stored in > the module/function/basicblock that they belong to. And that SHOULD, > assuming llvm-dis does what it is expected to do, be the same order. > Thanks for the reply. What about instruction ordering across basic blocks?

Hi! A few weeks ago, I have uploaded a new R package "frontier" for Stochastic Frontier Analysis (SFA) [1] to CRAN [2]. It includes the FORTRAN code of Tim Coelli's [3] software "Frontier 4.1" [4]. Hence, the R package "frontier" should have the same capabilities as "Frontier 4.1", i.e. Maximum Likelihood Estimation of Stochastic Frontier Production

Hi! A few weeks ago, I have uploaded a new R package "frontier" for Stochastic Frontier Analysis (SFA) [1] to CRAN [2]. It includes the FORTRAN code of Tim Coelli's [3] software "Frontier 4.1" [4]. Hence, the R package "frontier" should have the same capabilities as "Frontier 4.1", i.e. Maximum Likelihood Estimation of Stochastic Frontier Production

Dear all I am happy to announce that version 1.0 of the "frontier" package is available on CRAN. The R package "frontier" provides tools for analysing efficiency and productivity using the "stochastic frontier" approach. This R package is based on Tim Coelli's DOS software "FRONTIER 4.1" and has been available on CRAN for almost 5 years now. After many

My problem was that the constructor for DenseMap has an undocumented constraint. explicit DenseMap(unsigned NumInitBuckets = 0) { init(NumInitBuckets); } if given an explicit argument, requires that the argument be a power of 2. It's checked by an assert in init(), but for some reason my code didn't trip the assertion. Is there a special way I must make to enable asserts? Thanks,