search for: sphinxifying

...nx ======================================= As a few of you that are on IRC already know, I have experimented with moving the LLVM documentation over to `Sphinx <http://sphinx.pocoo.org/index.html>`__ from the current html form. I have moved almost all of the content over and have begun "Sphinxifying" the documentation to correct links and make use of the many features that Sphinx provides. What is Sphinx? --------------- To quote from the Sphinx website: Sphinx is a tool that makes it easy to create intelligent and beautiful documentation, written by Georg Brandl and licensed under...

...ormatting issues that should be fixed before this is rolled out. > #. Integrate building the docs into the autoconf and CMake build systems. Yes, this seems important. Also, the web page needs to auto-update the docs in response to commits. > #. Finish moving over the docs. > #. Finish Sphinxifying them. Can this be done incrementally? It would be great to start with one doc (like LangRef) and make it really really good and get the infrastructure right, then move on to other docs (which others might help out with). -Chris

...================= > > As a few of you that are on IRC already know, I have experimented with moving > the LLVM documentation over to `Sphinx <http://sphinx.pocoo.org/index.html>`__ > from the current html form. I have moved almost all of the content over and have > begun "Sphinxifying" the documentation to correct links and make use of the many > features that Sphinx provides. > > What is Sphinx? > --------------- > > To quote from the Sphinx website: > > Sphinx is a tool that makes it easy to create intelligent and beautiful > documentation,...

...================== > > As a few of you that are on IRC already know, I have experimented with moving > the LLVM documentation over to `Sphinx <http://sphinx.pocoo.org/index.html>`__ > from the current html form. I have moved almost all of the content over and have > begun "Sphinxifying" the documentation to correct links and make use of the many > features that Sphinx provides. > > What is Sphinx? > --------------- > > To quote from the Sphinx website: > >  Sphinx is a tool that makes it easy to create intelligent and beautiful >  documentation, wr...

.... > > Cool. Please pull this content into the ProgrammersManual as a new section. I've added a link to the new page where it used to say "it's out of the scope of this document [ProgrammersManual.html] to describe how to do this". Is that close enough? When I get around to Sphinxifying ProgrammersManual.html, I think the general approach is going to be to break the current top-level divisions into their own pages anyway, so this will be able to fit right in. The top level divisions of ProgrammersManual, like "Picking the Right Data Structure for a Task", are natural top...

...be fixed before this is rolled out. > >> #. Integrate building the docs into the autoconf and CMake build systems. > > Yes, this seems important.  Also, the web page needs to auto-update the docs in response to commits. > >> #. Finish moving over the docs. >> #. Finish Sphinxifying them. > > Can this be done incrementally?  It would be great to start with one doc (like LangRef) and make it really really good and get the infrastructure right, then move on to other docs (which others might help out with). BoostBook is a simplification of DocBook, with many things specifi...

On Fri, Jun 15, 2012 at 4:44 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > Am I the only one who thinks that it is impractical that the Sphinx intro is > buried deep within the lld documentation?  I suggest moving it to the > Programming Documentation document. Agreed that it needs to move to llvm proper, this was always the plan. I think the only thing we were waiting on was

Am I the only one who thinks that it is impractical that the Sphinx intro is buried deep within the lld documentation? I suggest moving it to the Programming Documentation document. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120616/2cb7356d/attachment.html>

On Oct 4, 2012, at 5:15 PM, Sean Silva <silvas at purdue.edu> wrote: >> It won't cause a negative effect, go for it! Dynamic_cast is realllly slow compared to dyn_cast, it is worth the memory. > > Ok, here's the first batch. It converts the RecTy hierarchy over to > use LLVM-style RTTI. Along the way, I also wrote up a new doc "How to > set up LLVM-style

...pdate the docs in response to commits. I'll need help integrating it into the build system. As for auto-update, I think Daniel (there's that name again) already has this somewhat setup. Again I don't know how to do this. > >> #. Finish moving over the docs. >> #. Finish Sphinxifying them. > > Can this be done incrementally?  It would be great to start with one doc (like LangRef) and make it really really good and get the infrastructure right, then move on to other docs (which others might help out with). > > -Chris Of course. I agree that it should be incremental....

> It won't cause a negative effect, go for it! Dynamic_cast is realllly slow compared to dyn_cast, it is worth the memory. Ok, here's the first batch. It converts the RecTy hierarchy over to use LLVM-style RTTI. Along the way, I also wrote up a new doc "How to set up LLVM-style RTTI for your class hierarchy", which covers the previously undocumented (albeit not that

Overhauling Attributes Problem ======= LTO needs a way to pass options through to different parts of the compiler. In particular, we need to pass code generation options to the back-end. The way we want to do this is via the LLVM Attributes class. In order to do that, we need to overhaul the Attributes class. The Attributes class right now isn't very extensible. After considering several