similar to: [LLVMdev] C Frontend doxygen docs

As I have been threatening: (http://mail.cs.uiuc.edu/pipermail/llvmdev/2002-October/000141.html) to do (http://mail.cs.uiuc.edu/pipermail/llvmdev/2002-September/000092.html) for some time now, I have regenerated the X86 and Sparc C frontends. They are now in-sync again and both emit the 'external' keyword instead of 'uninitialized' as appropriate (plus other changes). If you are

I'm trying to generate the declarations for function intrinsics, and I must be misunderstanding how to create new functions - I saw that a function with no basic blocks is treated as a declaration, so I tried to just create one and add it to the globals list: llvm_type *structTy, *ptrToStructTy; structTy = llvm_type_create_struct(0, 0); structTy =

You need to use -emit-llvm http://llvm.org/docs/GettingStarted.html#tutorial4 -Tanya On Thu, 21 Dec 2006, Jakob Praher wrote: > hi all, > > i surely overlooked something. > but i am currently trying to do some benchmarking stuff with llvm. > in my thesis i was using llvm-1.5 (i did some extension work, which i > would have to frontport now). > > But unfortunately 1.5 is

Need review on new docs build. The directory layout has changed, and the changes propagate through source, build, install and possible website levels. What follows is an overview of the changes and some reasoning behind them. [patch can be found under pr6613; you will need doxygen.sh, doxygen.patch, doxygen.txt] [read: doxygen.txt for full instructions] A build diagram is also available;

The LLVM 1.4 Release is now out! Get it here: http://llvm.cs.uiuc.edu/releases/ or read about it here: http://llvm.cs.uiuc.edu/releases/1.4/docs/ReleaseNotes.html#whatsnew This release features a huge assortment of improvements in functionality, generated code quality, and compile times. Thanks to everyone who has helped make this release the best one yet. In addition to the changes

Perhaps I am missing some link. Need a bit clarification. For the C language, I want to access the LLVM code immediately generated by llvmgcc(cfrontend/bin/gcc) before it undergoes any further transformation or optimization. 1) Are there any libraries that enable me to parse C code and create the Module instance. 2) If answer to 1) is no, then is there some other way to create Module

OK, I noticed a few problems with my previous email, so I will boil the question down: What I want to do is compile for x86 and ia64 from darwin. I also want to load my own passes into opt and llc. Should I be using llvmc at all here, or should I be doing something like llvmgcc -> gccas -> opt -> llc ? I've given up on the filetype=obj argument, so now the problem is that llc is

Chris Lattner wrote: >> I tried generating the docs myself ... doxygen simply refuses to >> create pages for classes defined in anonymous namespaces in cpp files. >> I enabled options such as EXTRACT_ALL, EXTRACT_PRIVATE and >> EXTRACT_LOCAL, but no luck. How is the publicly available >> documentation generated? > > They are generated from the Makefile in

hi all, i surely overlooked something. but i am currently trying to do some benchmarking stuff with llvm. in my thesis i was using llvm-1.5 (i did some extension work, which i would have to frontport now). But unfortunately 1.5 is for some benchmarks unstable (at least on my box) such that llc sigsegvs sometimes, etc. So I wanted to give 1.9 a go and build that on the my intel mac book. I did

On 9/1/06, Michael McCracken <michael.mccracken at gmail.com> wrote: > On 9/1/06, Chris Lattner <sabre at nondot.org> wrote: > > On Fri, 1 Sep 2006, Michael McCracken wrote: [snip] > Now f951 doesn't crash when compiling, but still can't compile the > libgfortran files. It now finds some syntax errors in a generated file > that's part of the intrinsics

On Tue, 15 Nov 2005, Sameer D. Sahasrabuddhe wrote: > The docs available on illuvium.com are different from the one's present in > the doxygen tarball on the same page ... can the tarball be generated from > the same docs as the browseable version? I considered crawling the > illuvium.com site, but it would be better to simply have a tarball available. Agreed. I have been

On 11/8/06, Warren Armstrong <warren.armstrong at anu.edu.au> wrote: > Hi all, > > I'm looking into using LLVM to do some optimisations of > Fortran code. As part of this, I've been trying to build > the frontend with f95 support. At the moment, I'm trying > to resolve undefined symbol problems for code defined in > c-common.c + elsewhere - I'm taking

Chris and everyone else, Below I summarize my understanding of what llvm does when converting to SSA and a clarification on why backward dataflow analyses can not be performed on "just" SSA. >> Scalar variables still have a stack location associated with them, >> don't they? > > No, they don't. All scalar values in LLVM represent "virtual >

On Sat, 10 Jul 2004, Ramu Ramamurthy wrote: > LLVM is an excellent piece of work, Thanks! > LLVM is one of the few project I know that has used the mysterious GCC > front-end. I think it will be a great contribution to the community if > you could writeup and document how to interface to the GCC front-end > data-structures (like LLVM has done). Specifically: > > a)

Hi, The docs available on illuvium.com are different from the one's present in the doxygen tarball on the same page ... can the tarball be generated from the same docs as the browseable version? I considered crawling the illuvium.com site, but it would be better to simply have a tarball available. I tried generating the docs myself ... doxygen simply refuses to create pages for classes

On Mon, 3 Apr 2006, Michael McCracken wrote: > the bytecode with lli - I get the following error: > > $ lli -load=/home/mmccrack/linux/lib/libTau.sh leo-inline-300-tau.bc > ERROR: Program used external function > '__llvm_cxxeh_allocate_exception' which could not be resolved! This is most likely because you are trying to link with llvmgcc, not with llvm-g++. Make sure that

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1335345862 -3600 # Node ID 057516cb84336da09fe3163aeeb9039cf4d20c26 # Parent 5d796144e8a276ea843c5ad5ec4ae678194d50f3 docs: use "a4" not "a4wide" paper type for doxygen and latex a4wide is no longer shipped in texlive. Reported by Bastian Blank Signed-off-by: Ian Campbell

The LLVM tools are not includeed in the online Doxygen documentation. Only docs. include and lib are there. Could somone correct this if at all possible please :) Thanks, Aaron -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090315/bd1e364d/attachment.html>

Excellent work, this greatly improves the clarity of the generated docs. I would love it if the inheritance diagrams were kept as they are and the collaboration diagrams were hidden under a knob. Thanks, John On Fri, Apr 30, 2010 at 8:54 AM, mike-m <mikem.llvm at gmail.com> wrote: > Hi, I'm working on a patch to overhaul docs+doxygen builds for both llvm > and clang source

Thanks for the info, Philip. I will update the LLVM Programmer’s Manual first. Regards, chenwj Wei-Ren Chen (陳韋任) Homepage: https://people.cs.nctu.edu.tw/~chenwj 2017-04-02 18:11 GMT+08:00 Philip Pfaffe <philip.pfaffe at gmail.com>: > Hi chenwj, > > http://llvm.org/doxygen/Statistic_8h_source.html is the correct one. The > other two are remnants from older doxygen deployments.