similar to: [LLVMdev] Documentation Issues Welcome?

Displaying 20 results from an estimated 2000 matches similar to: "[LLVMdev] Documentation Issues Welcome?"

2006 Feb 28
1
[LLVMdev] Using llvm-gcc with a simple program and the '-c' option
Reid Spencer wrote: > On Mon, 2006-02-27 at 20:43 -0800, Wink Saville wrote: > >>> Try passing "-L/opt/llvm-1.6/llvm-gcc/lib/ -lcrtend" to llvm-ld. >>> >> This didn't work for me: >> llvm-ld -o t1.app t1.bc t1.a -L/opt/llvm-1.6/llvm-gcc/lib/ -lcrtend.a >> >> I get two warning's about library 'crtend' missing
2003 Nov 23
3
[LLVMdev] Linkage Types again!
The problem I'm experiencing with Stacker has to do with linkage types (again!). What I'm trying to do is create a "global appending" array. In compilation units that don't include "main", I generate it with: TheStack = new GlobalVariable( /*type=*/ stack_type, /*isConstant=*/ false, /*Linkage=*/
2006 Feb 28
0
[LLVMdev] Using llvm-gcc with a simple program and the '-c' option
On Mon, 2006-02-27 at 20:43 -0800, Wink Saville wrote: > > Try passing "-L/opt/llvm-1.6/llvm-gcc/lib/ -lcrtend" to llvm-ld. > This didn't work for me: > llvm-ld -o t1.app t1.bc t1.a -L/opt/llvm-1.6/llvm-gcc/lib/ -lcrtend.a > > I get two warning's about library 'crtend' missing > You didn't get the instructions quite right. The option is
2006 Feb 28
3
[LLVMdev] Using llvm-gcc with a simple program and the '-c' option
Chris Lattner wrote: > On Sun, 26 Feb 2006, Wink Saville wrote: >> I then do the following in my makefile: >> >> llvm-gcc -c t1.c -o t1.bc >> llvm-gcc -c t1sub1.c -o t1sub1.bc >> llvm-gcc -c t1sub2.c -o t1sub2.bc >> llvm-ar r t1.a t1sub1.bc t1sub2.bc >> llvm-ar: creating t1.a >> llvm-ld -o t1.app t1.bc t1.a /opt/llvm-1.6/llvm-gcc/lib/libcrtend.a
2003 Nov 23
0
[LLVMdev] Linkage Types again!
> That's essentially what I did to get it to work but instead of > appending, I just opted for LinkOnce. Sounds ok. > > I don't quite understand why you need an appending global to do this, if you > > can only have one main. I would just set it to the correct initializer in the > > module that has main, and leave it external everywhere else. > > Its
2004 Aug 30
1
[LLVMdev] llvmc - Compiler Driver - Status Update & Issues
Folks, As of the writing of this note, the llvmc tool is enabled for build on the CVS head. I'm encouraging you to try it out, provide some feedback, and help with the issues below. llvmc is now able to correctly link a pure bytecode version of any Stacker program. This includes translation with stkrc, optimization with opt and linking with llvm-link. It is also able to find Stacker's
2004 Jul 21
2
[LLVMdev] GC questions.
On Wed, 21 Jul 2004, Tobias Nurmiranta wrote: > > Hi, I'm thinking out loud, please give me some feedback. > > Regarding llvm.gcread and llvm.gcwrite, wouldn't it be nicer if they are > implemented as: > > llvm.gcread(sbyte** object, uint offset) > llvm.gcwrite(sbyte* data, sbyte** object, uint offset) > > Where you also have the offset into the object. In
2004 Jul 21
0
[LLVMdev] GC questions.
Ok, that makes sense :). , Tobias On Wed, 21 Jul 2004, Chris Lattner wrote: > On Wed, 21 Jul 2004, Tobias Nurmiranta wrote: > > > void *llvm_gc_read(void *ObjPtr, void **FieldPtr) { > > > return *FieldPtr; > > > } > > > > Hm, but doesn't FieldPtr need to be calculated target-specific in those > > cases? > > For the field pointer, one
2004 Jul 21
2
[LLVMdev] GC questions.
On Wed, 21 Jul 2004, Tobias Nurmiranta wrote: > > void *llvm_gc_read(void *ObjPtr, void **FieldPtr) { > > return *FieldPtr; > > } > > Hm, but doesn't FieldPtr need to be calculated target-specific in those > cases? For the field pointer, one could use the getelementptr instruction: %pairty = { sbyte, sbyte, int* } %pairPtr = ... %fieldptr = getelementptr
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
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
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 >
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 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 ...
> 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> >
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
2005 May 19
0
[LLVMdev] [Cygwin] groff build error
Aaron, This looks to be exactly the same problem as with the executables. There's probably a space where it shouldn't be. Either that or the CommandGuide directory isn't getting created properly. Reid On Thu, 2005-05-19 at 23:12 +0100, Aaron Gray wrote: > Here it is, a missing file "analyze.1" :- > > /usr/bin/groff -Tps -man
2004 Jul 21
0
[LLVMdev] GC questions.
On Wed, 21 Jul 2004, Chris Lattner wrote: > > Yes, this makes a tremendous amount of sense. Do you think you could > prepare some patches to make this happen? If you have any questions, feel > free to ask :) Ok, a patch[1] is attached. I didn't care to coerce the offset, since I assume that it is an uint, but maybe I should? Hopefully I've understood the llvm source
2013 May 24
3
[LLVMdev] Installing LLVM Tools
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 (http://llvm.org/docs/CommandGuide/)). I have downloaded LLVM, Clang, the test suite, and have run the build and make commands. I have looked around on the website but I have not found a sufficient
2005 Apr 22
0
[LLVMdev] tabs
I found 179 more *.{c,cpp,h} files with tabs. Unfortunately, the tabs stops used vary so blindly expanding them messes up alignment in many cases :( Index: examples/BFtoLLVM/BFtoLLVM.cpp Index: include/llvm/AbstractTypeUser.h Index: include/llvm/GlobalVariable.h Index: include/llvm/InstrTypes.h Index: include/llvm/IntrinsicInst.h Index: include/llvm/ADT/PostOrderIterator.h Index: