search for: djone

...x but I've encountered the following errors while trying to configure R on my 2.6 box. Any assistance would be appreciated. ld: fatal: Symbol referencing errors. No output written to R.bin *** Error code 1 make: Fatal error: Command failed for target `R.bin' Current working directory /home/djones/R-1.3.1/src/main *** Error code 1 make: Fatal error: Command failed for target `R' Current working directory /home/djones/R-1.3.1/src/main *** Error code 1 make: Fatal error: Command failed for target `R' Current working directory /home/djones/R-1.3.1/src *** Error code 1 make: Fatal error...

...pl/libappl.a(dsvdc.o) dgemm_ array.o dasum_ ../appl/libappl.a(dpoco.o) ld: fatal: Symbol referencing errors. No output written to R.bin *** Error code 1 make: Fatal error: Command failed for target `R.bin' Current working directory /home/djones/R-1.3.1/src/main *** Error code 1 make: Fatal error: Command failed for target `R' Current working directory /home/djones/R-1.3.1/src/main *** Error code 1 make: Fatal error: Command failed for target `R' Current working directory /home/djones/R-1.3.1/src *** Error code 1 make: Fatal error...

On 22 February 2015 at 20:58, David Jones <djones at xtreme-eda.com> wrote: > Not sure if this is your problem, but it was mine: > > You must create (or obtain) a DataLayout *and install it into the Module*. > > It is possible to generate machine code for IR and not install the > DataLayout into the Module. Rather, the DataLa...

I'm upgrading my application to use LLVM 3.7.1 instead of 3.5.1. On one of my regression tests I am getting an assertion: /home2/djones/llvm-3.7.1.src/lib/IR/Metadata.cpp:490: void llvm::MDNode::resolve(): Assertion `isUniqued() && "Expected this to be uniqued"' failed. This occurs when finalizing debug info prior to code generation: #4 0x00007ffff4520455 in llvm::MDNode::resolve() () from /tools/llvm/3.7....

Is there any intention of making floating absolute and negate primitive IR instructions? I ask because only a few days ago I was also faced with the task of implementing negate in my compiler, and finding no suitable IR instruction, simply subtracted from zero. But this is wrong. I could change my code to do the bit casting and fiddling, but I wonder: would that be lowered appropriately on all

Is there a simple example of how to add debug metadata to IR using the C++ API? All I really need right now is the ability to annotate an instruction with line number and file name, although describing variables will be useful later. It's not clear from reading the include files how to "put it all together". Unfortunately, the output of my compiler is getting a little large to

...those things out (they get provided by your project via callbacks), but you do have to provide those features or avoid parsing code that would need them. If you can get the job done by working in Python using the ast module, I would recommend that. On Sat, Jul 4, 2015 at 5:58 AM, David Jones <djones at xtreme-eda.com> wrote: > There is also the Pyston project from Dropbox. Presumably that includes a > Python parser. > > I'm not affiliated with the project. > > On Sat, Jul 4, 2015 at 2:35 AM, Alec Taylor <alec.taylor6 at gmail.com> > wrote: > >> Than...

Thanks - I'll try this tonight. Assuming it works, should these variables be added to the docs at http://llvm.org/docs/CMake.html ? On Wed, Jan 13, 2016 at 10:26 PM, Andrew Wilkins <axwalk at gmail.com> wrote: > > > On Thu, 14 Jan 2016 at 11:02 David Jones via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> Now that autoconf is going away soon, I

Trying to figure out how to configure it for multiple users. By default CentOS doesn't have a daemon setup if you want to do this. Preston

What is the preferred method for compiler (frontend) developers to optimize and generate target machine code from IR? At one point I found a tutorial that recommended simply dumping the IR to a file and spawning llc to do the job. Up until now I have "manually" created a TargetMachine, PassManager, etc. to generate my object code. The initial version of my code was cribbed from llc for

On 23 February 2015 at 11:22, David Jones <djones at xtreme-eda.com> wrote: > You have not installed the DataLayout in the Module, as I had pointed out > earlier. > Hi David, I reported earlier that I tried this but there was no improvement. Well I ran another test to be sure. The results are below. As you can see the loads are stil...

Hmm... found an interesting issue: Given: %2 = getelementptr inbounds %UodStructType* %0, i32 0, i32 0 store i8 1, i8* %2, align 8 %3 = getelementptr inbounds %UodStructType* %0, i32 0, i32 1 store i8 2, i8* %3, align 1 %4 = getelementptr inbounds %UodStructType* %0, i32 0, i32 2 store i8 3, i8* %4, align 2 %5 = getelementptr inbounds %UodStructType* %0, i32 0, i32 3

...ersion of LLVM and its libraries yourself' - that is indeed what I did on my own machine (Ubuntu 14.04 apt-get thinks 3.4 is latest, so I'm currently building 3.8 from source) - but how would you recommend doing this on a user's machine? On Wed, Mar 23, 2016 at 5:17 PM, David Jones <djones at xtreme-eda.com> wrote: > Given that the LLVM API changes constantly, any reasonable C++ program may > very well compile properly against only one specific version/release of > LLVM. The probability that you can properly build against whatever some > user has installed on some ar...

Given that the LLVM API changes constantly, any reasonable C++ program may very well compile properly against only one specific version/release of LLVM. The probability that you can properly build against whatever some user has installed on some arbitrary system approaches zero. If you accept this, then you likely work around it by configuring and installing an appropriate version of LLVM and its

Hi, I am generating following code: %base = getelementptr inbounds %ravi.CallInfo* %6, i32 0, i32 4, i32 0 %7 = load %ravi.TValue** %base %8 = bitcast %ravi.TValue* %7 to i8* %9 = bitcast %ravi.TValue* %5 to i8* call void @llvm.memcpy.p0i8.p0i8.i32(i8* %8, i8* %9, i32 16, i32 8, i1 false) %10 = load %ravi.CallInfo** %L_ci %base1 = getelementptr inbounds %ravi.CallInfo* %10, i32 0,

Further to my previous email, I now have some answers. The culprit is the IR verifier. 1. opt -time-passes does not report time spent in the IR verifier. If I add -disable-verify, opt's run time drops from 71 seconds to 37 seconds. 2. -disable-verify doesn't disable all verification runs. The IR verifier is run 3 times: once prior to any optimization work, once between running the

I've got a i7 with 12 logical cores and 16GB of RAM I successfully built RELEASE_390/final but for the last 100 or so files I'd to use "ninja -j2" so as not to keep from swapping in the best case and and in the worst case the build kills itself without completing because apparently its run out of memory. For the first 3200 files or so it was doing just fine with

...n C/C++? Ie, there's no fneg() in libm, so any C method we choose could cause an exception, and that's not allowed by the IEEE definition of fneg. On Fri, Aug 8, 2014 at 12:29 PM, Stephen Canon <scanon at apple.com> wrote: > > > On Aug 8, 2014, at 11:22 AM, David Jones <djones at xtreme-eda.com> wrote: > > > > A quick survey from my various manuals: > > - m68k has negate and absolute value instructions. > > - so does x87 > > - so does PA-RISC > > - but SPARC does not. > > - and neither does x86 SSE (although bit fiddling migh...

How do you disable optimization for a function? I ask because my application often compiles machine-generated code that results in pathological structures that take a long time to optimize, for little benefit. As an example, if a basic block has over a million instructions in it, then DSE can take a while, as it is O(n^2) in the number of instructions in the block. In my application (at least),

...l. David why do you say it is particularly bad IR (other than not having gone through SROA). Is it the multiple blocks for early returns? That is how I'm supporting early returns in the middle of a basic block. I couldn't find any other way. On Sun, Apr 5, 2015 at 6:24 AM, David Jones <djones at xtreme-eda.com> wrote: > Data point: > > I use (rarely) alloca in basic blocks other than the entry block, and it > works. > > The one point to be aware of: alloca is "cleaned up" only when the > function returns. If you use alloca in a loop, and you have no o...