Displaying 20 results from an estimated 3000 matches similar to: "[LLVMdev] Problem with the installation of llvm gcc"
2010 Apr 19
0
[LLVMdev] Problem with the installation of llvm gcc
You need to manually copy the llvm-gcc front-end binaries to somewhere
in your path. Alternatively, you can download the clang front-end and
start using that instead.
On Mon, Apr 19, 2010 at 10:58 AM, khaled hamidouche
<khaledhamidouche at gmail.com> wrote:
> Hello
>
> I'm trying to install LLVM and LLVM GCC
> so I check out the source of llvm and llvm-gcc-4.2 from the svn
2010 Apr 19
0
[LLVMdev] Problem with the installation of llvm gcc
khaled hamidouche wrote:
> Hello
>
> I'm trying to install LLVM and LLVM GCC
> so I check out the source of llvm and llvm-gcc-4.2 from the svn
>
> I flow the instructions of this page
> http://llvm.org/docs/GCCFEBuildInstrs.html
>
> I did the installation of LLVM and LLVM GCC well but the problem is
> there is no llvm-gcc at the end of instalation !!! ??
>
2010 Apr 20
1
[LLVMdev] iterate over loops inside the runOnFunction
Hello
I'm wandring to write a Function parser that iterates over loops inside each
function and inside each loop iterates over instructions
So I found a way to do the Function parser that iterates over BasicBlocks
(using the runOnfunction Pass) but I no know how make it iterates over
loops ?
So my question is there any way to make a loop inside the runOnfunction to
iterate over
2010 Apr 21
2
[LLVMdev] determining the number of iteration of a loop
Hello
I'm wandring to know how many times a block is executed inside a loop ?
knowing that I can't use getSmallConstantTripCount() because the number is
unkown "for (i=0;i<N;i++) for example"
I'm using a Function pass
for (Function::iterator BB = F.begin(), E = F.end(); BB != E; ++BB) {
if (Loop *L = LI->getLoopFor(BB)) {
if (L->getHeader() ==
2010 Apr 21
0
[LLVMdev] determining the number of iteration of a loop
On Apr 21, 2010, at 7:31 AM, khaled hamidouche wrote:
> I'm wandring to know how many times a block is executed inside a
> loop ?
> knowing that I can't use getSmallConstantTripCount() because the
> number is unkown "for (i=0;i<N;i++) for example"
In general, the number of iterations is undecidable. For example:
int main(char **argv, int N) {
for
2010 Apr 23
1
[LLVMdev] How to get the Operand type
Hello
How to get the type of an Operand ?
so for example I want to get the type of the operand(0) in this istruction
%arrayidx22 = getelementptr [1000 x double]* %C, i64 0, i64 %indvar67 ;
<double*> [#uses=1]
I tried (II->getOperand(0))->getType() ) but this give me an adress (I
think) (some think like 0x1253.. )
also I tried to get the type of the instruction with
switch
2010 Apr 23
1
[LLVMdev] pass argument to a FunctionPass
Hello
is there any way to pass argument to my own Function pass
I mean I wrote a Function pass (like Hello) that give me somme analyzes
about the code source and I need to pass somme argument to the Pass like
the size of data....
I want some think like this
opt -load ../../../Debug/lib/LLVMHello.so -hello2 < test.bc > /dev/null
arg1 arg2 ...
So how to get inside the Function pass the
2010 Aug 31
2
[LLVMdev] Using LLVM with Ada
Dear all,
I'm trying to exploit the LLVM framework to optimize my Ada programs.
To this extent I compiled the Ada f-e from source (v. 2.5).
However, while trying to compile a simple HelloWorld example I get several
errors dealing with undefined references (while invoking LLVM on hello).
Arguably I missed something on the right way to use the LLVM tools
with Ada sourcecode.
I would really
2010 Aug 31
0
[LLVMdev] Using LLVM with Ada
Hi Enrico, did you follow the instructions here
http://llvm.org/docs/GCCFEBuildInstrs.html#ada
to build llvm-gcc with Ada support?
> To this extent I compiled the Ada f-e from source (v. 2.5).
If by 2.5 you mean LLVM-2.5 I suggest you use something more recent, for
example LLVM-2.7.
> However, while trying to compile a simple HelloWorld example I get several
> errors dealing with
2012 Jul 10
2
[LLVMdev] Unable to do even basic Clang tutorial
Looks like your make/install is incomplete wrt clang. I follow the
instuctions for checking out the sources but build using cmake instead
of configure:
> cmake -G ""Unix Makefiles" -DLLVM_TARGETS_TO_BUILD="X86" -DCMAKE_BUILD_TYPE="Release" -DCMAKE_INSTALL_PREFIX="../bin" ../llvm
> make install
This builds and installs llvm+clang in the bin
2008 Oct 23
4
[LLVMdev] Windows build broken?
Folks,
It appears the Windows build has regressed over the past week.
The build fails quite early (during the "Performing TableGenStep"
phase).
Any help/pointers would be appreciated.
Thanks,
snaroff (a clang developer)
2008 Oct 23
0
[LLVMdev] Windows build broken?
steve naroff <snaroff at apple.com> writes:
> Folks,
>
> It appears the Windows build has regressed over the past week.
>
> The build fails quite early (during the "Performing TableGenStep"
> phase).
>
> Any help/pointers would be appreciated.
It breaks for me because the usage of INT64_C, which was introduced on
r57663 and 57668.
Some googling around
2012 Jul 10
3
[LLVMdev] Unable to do even basic Clang tutorial
Add -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS to your compilation flag.
On 7/10/2012 11:23 AM, NY Knicks Fan wrote:
> Hi Ashok,
>
> I created a new Ubuntu 12.04 virtual machine and followed directions
> except that I know use your cmake command instead of configure, and I
> got the error below.
>
> Any help is very much appreciated.
>
>
> $
2012 Jul 10
0
[LLVMdev] Unable to do even basic Clang tutorial
Hi Ashok,
I created a new Ubuntu 12.04 virtual machine and followed directions except that I know use your cmake command instead of configure, and I got the error below.
Any help is very much appreciated.
$ /home/ubuntu/bin/bin/clang++ -I /home/ubuntu/bin/include/ tutorial1.cpp
In file included from tutorial1.cpp:5:
In file included from /home/ubuntu/bin/include/llvm/Support/raw_ostream.h:17:
2012 Jul 10
2
[LLVMdev] Unable to do even basic Clang tutorial
You will need to link to the LLVM/clang libraries. To get the correct
flags, you can run:
./llvm-config --ldflags --libs
and use the flags reported.
On 7/10/2012 11:35 AM, NY Knicks Fan wrote:
> OK. Thanks. I now get the following error (which appears to be a
> problem w/ the tutorial itself?):
>
> $ /home/ubuntu/bin/bin/clang++ -I /home/ubuntu/bin/include/
>
2012 Jul 10
0
[LLVMdev] Unable to do even basic Clang tutorial
OK. Thanks. I now get the following error (which appears to be a problem w/ the tutorial itself?):
$ /home/ubuntu/bin/bin/clang++ -I /home/ubuntu/bin/include/ -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS tutorial1.cpp/tmp/tutorial1-LQ71fW.o: In function `main':
tutorial1.cpp:(.text+0x42): undefined reference to `llvm::outs()'
tutorial1.cpp:(.text+0x72): undefined reference to
2012 Jul 10
2
[LLVMdev] Unable to do even basic Clang tutorial
You need to link in the libclang* as well.
On 7/10/2012 1:22 PM, NY Knicks Fan wrote:
> Hi Ashok,
>
> $ cd bin/bin
> $ ./llvm-config --ldflags --libs
> -L/home/ubuntu/bin/lib -ldl -lpthread
> -lLLVMAsmParser -lLLVMTableGen -lLLVMDebugInfo -lLLVMX86Disassembler
> -lLLVMX86AsmParser -lLLVMX86CodeGen -lLLVMSelectionDAG -lLLVMAsmPrinter
> -lLLVMX86Desc -lLLVMX86Info
2012 Jul 10
0
[LLVMdev] Unable to do even basic Clang tutorial
Hi Ashok,
$ cd bin/bin
$ ./llvm-config --ldflags --libs
-L/home/ubuntu/bin/lib -ldl -lpthread
-lLLVMAsmParser -lLLVMTableGen -lLLVMDebugInfo -lLLVMX86Disassembler -lLLVMX86AsmParser -lLLVMX86CodeGen -lLLVMSelectionDAG -lLLVMAsmPrinter -lLLVMX86Desc -lLLVMX86Info -lLLVMX86AsmPrinter -lLLVMX86Utils -lLLVMJIT -lLLVMMCDisassembler -lLLVMMCParser -lLLVMInstrumentation -lLLVMInterpreter
2008 Oct 23
2
[LLVMdev] Windows build broken?
Óscar Fuentes <ofv at wanadoo.es> writes:
>> It appears the Windows build has regressed over the past week.
>>
>> The build fails quite early (during the "Performing TableGenStep"
>> phase).
>>
>> Any help/pointers would be appreciated.
>
> It breaks for me because the usage of INT64_C, which was introduced on
> r57663 and 57668.
>
2020 Mar 06
1
Re: [PATCH nbdkit 2/4] server: Add nbdkit_shutdown() call.
On 3/4/20 9:17 AM, Richard W.M. Jones wrote:
> Plugins and filters may call this to initiate an asynchronous shutdown
> of the server. This would only be used in the connected phase —
> plugins should still call exit(3) directly for configuration failure.
>
> It is equivalent to sending a kill signal to self, but it's cleaner to
> have an API for this and better for