similar to: [LLVMdev] Doxygen not up to date?

On 10/14/13 5:53 AM, Abhinash Jain wrote: > How can I generate a new function at compile time and insert some instruction > onto it, through llvm pass. > eg. > > 1) %y = alloca i32, align 4 > 2) %z = alloca i32, align 4 > 3) %t = alloca i32, align 4 > 4) %2 = load i32* %y, align 4 > 5) %3 = load i32* %z, align 4 > 6) %add = add nsw i32 %2, %3 > 7) %4 = load

Hi all, I'm having a bit of trouble with the online doxygen documentation. As far is I know, it should reflect current svn trunk. However, it seems out of date. For example, the ExtractValueInst [1] is not a UnaryInstruction yet and still takes Value* as indices. To add to the confusing, the mainpage [2] says it is documentation version "2.1svn" which seems even more weird. What

In my quest to account for memory, I've now come to the in-memory IR, and the generated code. I want to book the generated code memory against the agent that is generating the code. I see that LLVM's Function class [1] has a size function; what does this represent and can I use it to account for the space used by the in-memory IR? As for generated code, the JIT [2] class simply returns a

> I'm having a bit of trouble with the online doxygen documentation. As far is I > know, it should reflect current svn trunk. However, it seems out of date. For > example, the ExtractValueInst [1] is not a UnaryInstruction yet and still > takes Value* as indices. > > To add to the confusing, the mainpage [2] says it is documentation version > "2.1svn" which seems

On Sep 28, 2007, at 10:27 AM, Sandro Magi wrote: > In my quest to account for memory, I've now come to the in-memory IR, > and the generated code. I want to book the generated code memory > against the agent that is generating the code. > > I see that LLVM's Function class [1] has a size function; what does > this represent and can I use it to account for the space used

Hi Syoyo, > I am trying to get a return type of a function(from bitcode file) with > LLVM-C API, but there seems no appropriate API to do that. From my memory, this info is stored in the function type, so you could look at the function's type and get the info there. Looking the the API docs [1], I find that there is a simple method on Function called getReturnType(). You should thus be

Hi folks, Hope this is not a silly question. But it bothers me when I am thinking about it. My question is: 1. In the implementation of serverSplitPHINodes(), why it only checks the first PHI node for possible multiple inputs from outside the region to extract. There could be more than one PHI nodes in the header block, and the code only checks the first one. I don't quite get it.

Are you perhaps not calling void Function::setSubprogram (DISubprogram * SP) http://llvm.org/doxygen/classllvm_1_1Function.html#a05a19abc8ee11d5909275d980efa1670 ? -- adrian > On Nov 18, 2016, at 8:46 AM, David Blaikie <dblaikie at gmail.com> wrote: > > (+Adrian who might have some more context here) > > Generally I'd suggest looking at Clang's code to see how

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

Dear Sir or Ms: My OS is ubuntu 12.04(AMD64). I have installed TexLive 2012, Graphviz 2.26.3, doxygen 1.7.6.1 without the dependence doxygen-latex.The version of LLVM I am working on is 3.2. My configure script is the following: ../llvm-3.2/configure --prefix=/home/me/mywork/sca/llvm/llvm-install2 --enable-targets=host-only --enable-debug-runtime --enable-assertions --enable-doxygen

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.

CentOS Errata and Bugfix Advisory 2012:0718 Upstream details at : http://rhn.redhat.com/errata/RHBA-2012-0718.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 72c425f77c5c39f7acf6e022521cc85b76c394784e93f04188e0681251e6c592 doxygen-1.4.7-2.i386.rpm 97ea811c40a83bf5c7f30efe5394769206c61deb045b41477e0f0f3d96762a42

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;

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

Hi I've tried to get doxygen documentation by configuring with --enable-doxygen. Then 'make install' has been interrupted with message "error: configuration file /media/data/virtual/share/gsoc/build/docs/doxygen.cfg not found!". mikem, why did you remove a line "AC_CONFIG_FILES([docs/doxygen.cfg])" in autoconf/configure.ac [1] ? I've restored this line. Now

Hi, Here is a patch to update documentation to Doxygen 1.8.18 as the navbar is broken trying to use the latest Doxygen. Also seems we are missing documentation for last releases here: https://www.opus-codec.org/docs/ Best Regards Marcus -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi folks, I noticed that llvm.org currently hosts two instances of the doxygen API docs, [1] and [2]. Is that intentional or by accident? What's a bit vexing about this is that googling specific APIs always ends up on [2]. However, [2] hasn't been updated for a year now and [1] would be the correct hit. But /doxygen is Disallowed through robots.txt. Best, Philip [1]

Hi All, I am going to clean up those doxygen links on LLVM Programmer’s Manual [1], some are lost and some are too old. However, I am confused on which doxygen link I should pick up. I see there are mutiple links exist on LLVM web site for LLVM classes. Take class Statistic as example, there are: - http://llvm.org/doxygen/Statistic_8h-source.html (the oldest one, I believe it's

One thing that would be handy for driver developers (or for myself, at the very least) would be having some API documentation for the core NUT functions. Here is an example of Doxygen's output: http://www.ghz.cc/~clepple/libhid/doc/html/hid_8h.html The two main categories of API documentation that I see are the internal NUT functions needed for writing drivers, etc., and the external

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