search for: linktim

Hello all, I'm a research assistant at the University of Wisconsin and we're trying to come up with a general way to run our whole program analysis over programs that may use different methods to perform the build. I saw some discussion that liblto could be used for this (and safecode successfully did it) for llvm 2.6 - 3.0, but that doesn't seem to be working the same way with llvm

...I understand that neither can handle the very large Google applications, but that's probably not a near-term concern for a project like the one Charles is embarking on. Vikram, LLVM can handle Firefox size programs. Honza wrote two good articles about LTO. http://hubicka.blogspot.com/2014/04/linktime-optimization-in-gcc-1-brief.html http://hubicka.blogspot.com/2014/04/linktime-optimization-in-gcc-2-firefox.html Comparison with LLVM is described in the second article. It took about 40min to finish building Firefox with llvm using lto and -g. The following is a quote: "This graph shows is...

...inst, then you need '-ldl' because of OpenSSL, not because of OpenSSH. The only way for OpenSSH's ./configure to detect that OpenSSL needs '-ldl' is for OpenSSL to provide a pkgconfig <http://www.freedesktop.org/software/pkgconfig/> thingy that explains what OpenSSL's linktime needs are. Since openssl(-engine)?-0.9.6d doesn't provide that, you need to do so manually. If there's nothing in OpenSSL's documentation that explains OpenSSL's linktime needs, then please file a bug report with OpenSSL. ------- You are receiving this mail because: ------- Yo...

...ould change the IR to "4$0". > > LLVM appears to be optimizing the addressing mode, and the optimizer > is being more lenient on this detail so you're getting lucky when the > +4 can be combined with an existing %rsp offset. Things break down when part of the offset is a linktime constant: ``` source_filename = "asanasm.d" target datalayout = "e-m:w-i64:64-f80:128-n8:16:32:64-S128" target triple = "x86_64-pc-windows-msvc" @globVar = global [2 x i32] [i32 66051, i32 66051] define void @_D7asanasm8offconstFZv() { call void asm sideeffect &q...

...test-suite version has no features to run custom metrics and generate other report type, right? > > Are these features of make-version of test-suite planned to be added? The lit test-suite runner supports arbitrary metrics, it already features codesizes for different segments, compiletime, linktime, executable hash, execution time. I designed it be easily extensible with further metrics. Not all of these metrics are understood by LNT yet so they may get lost after submission to an LNT database. We do not use GenerateReport.pl and friends in the cmake/lit version anymore, as the main data co...

...make. Cmake test-suite version has no features to run custom metrics and generate other report type, right? Are these features of make-version of test-suite planned to be added? The lit test-suite runner supports arbitrary metrics, it already features codesizes for different segments, compiletime, linktime, executable hash, execution time. I designed it be easily extensible with further metrics. Not all of these metrics are understood by LNT yet so they may get lost after submission to an LNT database. We do not use GenerateReport.pl and friends in the cmake/lit version anymore, as the main data co...

...e > just too massive for the kind of linking done by LTO. > > When we built GCC's LTO, we were trying to address this by creating a > partitioned model, where the analysis phase and the codegen phase are split > to allow working on partial callgraphs > (http://gcc.gnu.org/wiki/LinkTimeOptimization for details). > > This allows to split and parallelize the initial bytecode generation and the > final optimization/codegen. However, the analysis is still implemented as a > single process. We found that we cannot even load summaries, types and > symbols in an efficient...

...eatures to run custom metrics and generate other > report type, right? > > > > Are these features of make-version of test-suite planned to be added? > > The lit test-suite runner supports arbitrary metrics, it already features > codesizes for different segments, compiletime, linktime, executable hash, > execution time. I designed it be easily extensible with further metrics. > Not all of these metrics are understood by LNT yet so they may get lost > after submission to an LNT database. > > > > We do not use GenerateReport.pl and friends in the cmake/lit ve...

In openSUSE Tumbleweed (and several other distributions as well), packages are build by default with linktime optimization (LTO) enabled. This didn?t work for Dovecot, so until now LTO was disabled for Dovecot. There is a way to make it work though, see the following link: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997513#20 So far a fix has not made it to upstream, the latest version...

On Sep 24, 2013, at 9:13 AM, Joerg Sonnenberger wrote: > On Tue, Sep 24, 2013 at 10:49:36AM -0500, Shankar Easwaran wrote: >> Not sure why this is being done for a long time with the GNU linker. > > Because the main program is not PIC, it will only use absolute > references to global symbols. For functions, you can create a PLT > record, but for data access, you have to hide

...-suite version has no features to run custom metrics and generate other report type, right? > > Are these features of make-version of test-suite planned to be added? > The lit test-suite runner supports arbitrary metrics, it already features codesizes for different segments, compiletime, linktime, executable hash, execution time. I designed it be easily extensible with further metrics. Not all of these metrics are understood by LNT yet so they may get lost after submission to an LNT database. > > We do not use GenerateReport.pl and friends in the cmake/lit version anymore, as the m...

On Tue, Sep 24, 2013 at 10:49:36AM -0500, Shankar Easwaran wrote: > Not sure why this is being done for a long time with the GNU linker. Because the main program is not PIC, it will only use absolute references to global symbols. For functions, you can create a PLT record, but for data access, you have to hide the real symbol and copy the content over to the equivalent in the main binary.

On Sun, 30 Apr 2006, Aristid Breitkreuz wrote: > I am, as said in the subject, new to this list. I have not actually used > LLVM, I tried with an older version but failed. Recently I noticed that > 1.7 came out and looked at the release notes. And there was something > that stroke me: llvm-g++ adheres to the IA64 ABI but _not for > exceptions_. I was not able to find information why

Hello everyone, I am trying to add checkpoints to my IR code. In order to do that I need to add this instruction: call void @m5_checkpoint(i64 0, i64 0) to some of the basic blocks in my benchmark. m5_checkpoint is a function defined for checkpointing in another simulator and is not included in my benchmark source code. So I need to create this instruction and I couldn't figure out how to do

Hello, I am, as said in the subject, new to this list. I have not actually used LLVM, I tried with an older version but failed. Recently I noticed that 1.7 came out and looked at the release notes. And there was something that stroke me: llvm-g++ adheres to the IA64 ABI but _not for exceptions_. I was not able to find information why this is so and why it is necessary, so I hope you don't

Hi all, I stumbled upon either a bug, or we are emitting wrong inline asm code. The testcase is: ``` source_filename = "testcase.d" target datalayout = "e-m:o-i64:64-f80:128-n8:16:32:64-S128" target triple = "x86_64-apple-macosx" define void @_D7asanasm3fooFZv() { %a = alloca [4 x i32], align 32 call void asm sideeffect "movl %ebx, 4+$0",

...make. Cmake test-suite version has no features to run custom metrics and generate other report type, right? Are these features of make-version of test-suite planned to be added? The lit test-suite runner supports arbitrary metrics, it already features codesizes for different segments, compiletime, linktime, executable hash, execution time. I designed it be easily extensible with further metrics. Not all of these metrics are understood by LNT yet so they may get lost after submission to an LNT database. We do not use GenerateReport.pl and friends in the cmake/lit version anymore, as the main data co...

----- Original Message ----- > From: "James Molloy via llvm-dev" <llvm-dev at lists.llvm.org> > To: "Vaivaswatha Nagaraj" <vn at compilertree.com> > Cc: "LLVM Dev" <llvm-dev at lists.llvm.org> > Sent: Thursday, December 3, 2015 4:41:46 AM > Subject: Re: [llvm-dev] Function attributes for LibFunc and its impact on GlobalsAA > >

Hi all, As we understood great changes will be done in LNT, so we are waiting to new LNT version and stopped our work in LNT. One more question about using test-suite separately with cmake. Cmake can only build all tests and generate lit tests. After that we can run LIT and get report which is not equal with report (simple) got with make. Cmake test-suite version has no features to run custom