Displaying 20 results from an estimated 3000 matches similar to: "[LLVMdev] Installing LLVM Tools"
2013 May 24
0
[LLVMdev] Installing LLVM Tools
On Fri, May 24, 2013 at 3:27 PM, Kyle Holzinger <kholz at bu.edu> wrote:
> So I just started looking into LLVM and I was wondering how to install the
> LLVM tools suite. (Such as the llvm-as or lli commands in the terminal
> described here: http://llvm.org/docs/CommandGuide). I have downloaded
> LLVM, Clang, the test suite, and have run the build and make commands. I
> have
2007 Mar 28
2
[LLVMdev] Third party integration
I have only just begun looking through the docs for LLVM. I have read
through some of the PP presentations to get an idea of the modularity of
LLVM.
May someone be so kind to point me to some documentation on how to
communicate with the LLVM modules (specifically the optimizer) from some
third party piece of software (my compiler)?
I am hoping there is a file format, or some serialization, that
2013 May 17
2
[LLVMdev] AArch64 build error
Hi,
I'm getting a "random" build failure related to AArch64 when building with cmake. The build is running with -j32 so it seems that there is some dependency issue that causes the build to fail when things build in a certain order.
Is anyone else seeing this problem?
paul
3008 make[2]: *** No rule to make target `lib/Target/AArch64/AArch64GenDAGISel.inc', needed by
2013 May 17
0
[LLVMdev] AArch64 build error
Hi Paul,
> I'm getting a "random" build failure related to AArch64 when building with cmake.
> The build is running with -j32 so it seems that there is some dependency issue
> that causes the build to fail when things build in a certain order.
> 3008 make[2]: *** No rule to make target `lib/Target/AArch64/AArch64GenDAGISel.inc', needed by
Hmm. That file's
2005 May 19
6
[LLVMdev] [Cygwin] groff build error
Here it is, a missing file "analyze.1" :-
/usr/bin/groff -Tps -man /usr/build/llvm/docs/CommandGuide/analyze.1 > /usr/buil
d/llvm/docs/CommandGuide/analyze.ps
troff: fatal error: can't open `/usr/build/llvm/docs/CommandGuide/analyze.1': No
such file or directory
make[2]: *** [/usr/build/llvm/docs/CommandGuide/analyze.ps] Error 1
make[2]: Leaving directory
2005 May 20
2
[LLVMdev] [Cygwin] groff build error - semi solved
Turns out I did not have Perl installed and hence no pod2man command, so it was not groff after all.
But 'true', what ever it does, does not seem to be working on Cygwin.
true pod2man --release=1.5 --center="LLVM Command Guide" /usr/build/llvm/../../src/llvm-1.5/docs/CommandGuide/analyze.pod /usr/build/llvm/docs/CommandGuide/analyze.1
'true' seems to behaving like a
2011 Nov 01
2
[LLVMdev] RFC: Upcoming Build System Changes
Am 01.11.2011 18:04, schrieb Joerg Sonnenberger:
> On Tue, Nov 01, 2011 at 11:09:41AM +0100, Joachim Durchholz wrote:
>> On the reasons why make-based builds are slow, Peter Miller has some
>> insight to offer:
>> http://miller.emu.id.au/pmiller/books/rmch/ .
>> I'm not sure how widely recognized that paper is. Maybe it's widely
>> known and today's
2005 May 20
0
[LLVMdev] [Cygwin] groff build error - semi solved
Aaron Gray wrote:
> Turns out I did not have Perl installed and hence no pod2man command, so
> it was not groff after all.
>
> But 'true', what ever it does, does not seem to be working on Cygwin.
>
> true pod2man --release=1.5 --center="LLVM Command Guide"
> /usr/build/llvm/../../src/llvm-1.5/docs/CommandGuide/analyze.pod
>
2011 Nov 02
0
[LLVMdev] RFC: Upcoming Build System Changes
Dear All,
We have a new 32 core machine, so I ran some numbers. These results are
for compiling all of LLVM and Clang in a Debug build from scratch. The
first number is the -j argument to make, and the rest is the result of
the bash builtin time command.
2: 1612.950u 161.293s 15:04.92 196.0% 0+0k 0+0io 0pf+0w
4: 1624.101u 164.121s 8:00.74 371.9% 0+0k 0+0io 0pf+0w
8:
2005 May 19
3
[LLVMdev] [Cygwin] llvm 'make install' build errors
Am back to the same llvm 'make install' errors as I had before :-
Two trivial ones, of uncreated directories :-
llvm[2]: Installing Debug /usr/llvm/bin/llvm-ranlib
/usr/bin/install: target `/usr/llvm/bin/llvm-ranlib' is not a directory
make[2]: *** [/usr/llvm/bin/llvm-ranlib] Error 1
make[2]: Leaving directory `/usr/build/llvm/tools/llvm-ranlib'
make[1]: ***
2016 Aug 09
2
[LTO] Bypass the integrated assembler ...
Hi Guys ,
We enabled the LTO on our code base and found that LTO uses the
integrated/builtin assembler to emit the final optimized code .O
(FileType= CGFT_ObjectFile) .
Can we bypass this semantic ,for something like you emit .S file
(FileType=CGFT_AssemblyFile),
Then we pass this .S file to our native assembler and the linker
.....any switch/ options do so ?
i.e something like as we have
2017 Aug 10
2
Is anyone experienced writing Sphinx documentation?
I've read through the docs, but honestly this is driving me crazy and I
shouldn't have to fight this hard to just to write some documentation.
Here's the problem:
Look at llvm/docs/CommandGuide/FileCheck.rst
I want to add a table of contents that looks like this [
http://llvm.org/docs/CMake.html] to that file. Nothing I've tried works.
(Also, no I'm not trying to add it in
2011 Nov 02
5
[LLVMdev] RFC: Upcoming Build System Changes
Hello John.
John Criswell <criswell at illinois.edu> writes:
[snip]
> I did not use CMake but the standard autoconf + Makefile build.
>
> Not sure if this helps, but here it is, for what it's worth.
Very interesting, thanks!
CMake introduces more parallelism and it would be great to see how much
impact it makes. If you can, please run the cmake build with -j32, just
to
2010 Jan 20
2
Error meaning
Hi r-users,
I have the following code to solve 4 simultaneous eqns with 4 unknowns using newton iteration method. But I got the error message:
pars <- c(1.15, 40, 50, 0.78)
newton.input2 <- function(pars)
{ ## parameters to estimate
alp <- pars[1]
b1 <- pars[2]
b2 <- pars[3]
rho <- pars[4]
f1 <- pars[1]*pars[2]
f2 <-
2016 Aug 09
2
[LTO] Bypass the integrated assembler ...
> On Aug 9, 2016, at 9:24 AM, Kevin Choi via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>
> -Wl,--plugin=LLVMgold.so,--plugin-opt=emit-llvm
This is totally Gold specific. The fact that he mentions using LTOCodeGenerator makes me think that he does not use Gold.
>
> http://llvm.org/docs/CommandGuide/opt.html <http://llvm.org/docs/CommandGuide/opt.html>
>
2020 Jun 24
5
R 4.0.1-4.0.2 built with Intel Composer 19.0-19.1.1, error in "make check" on CentOS 7.7
Hi there,
I initially asked about this on r-help and was told this might be a better venue. I?m not really convinced from reading the posting guide, but I?ll give it a shot. It was also suggested that the R-Project doesn?t really care about building with ?non-standard? compilers, but I can?t find any evidence of that on the website (indeed, there?s some mention of successful past builds, and the
2014 Apr 02
2
[PATCH v8 00/10] qspinlock: a 4-byte queue spinlock with PV support
On 04/02/2014 10:32 AM, Konrad Rzeszutek Wilk wrote:
> On Wed, Apr 02, 2014 at 09:27:29AM -0400, Waiman Long wrote:
>> N.B. Sorry for the duplicate. This patch series were resent as the
>> original one was rejected by the vger.kernel.org list server
>> due to long header. There is no change in content.
>>
>> v7->v8:
>> - Remove one unneeded
2014 Apr 02
2
[PATCH v8 00/10] qspinlock: a 4-byte queue spinlock with PV support
On 04/02/2014 10:32 AM, Konrad Rzeszutek Wilk wrote:
> On Wed, Apr 02, 2014 at 09:27:29AM -0400, Waiman Long wrote:
>> N.B. Sorry for the duplicate. This patch series were resent as the
>> original one was rejected by the vger.kernel.org list server
>> due to long header. There is no change in content.
>>
>> v7->v8:
>> - Remove one unneeded
2013 Mar 15
3
[LLVMdev] Can the FileCheck ignore spaces ?
Hi all:
I'm writing testcase for the MC layer regression in llvm, the
disassembled string is a bit complicate, for example:
"IALU.T0 (I0) = BIU0.DM ; REPEAT AT ( 2 ) ;;"
The spaces in the disassembled string is error-prone. Is there any
option to tell the FileCheck utility to ignore the spaces ?
Kind Regards.
Shawn.
2012 Jan 28
1
[LLVMdev] CommandGuide documentation points to outdated pages?
Hello,
I noticed something strange in the links from
http://llvm.org/docs/CommandGuide/index.html
They all point to HTML files in http://llvm.org/cmds/, which were last
updated on 11-May-2010. There were many updates to the CommandGuide
documents since that time, according to the SVN logs, however.
One manifestation of this problem is that a fix made in r147721
(07-Jan-2012) to one of the