similar to: llvm/docs/AMDGPUUsage.rst ERROR: Malformed table

On Tue, Feb 12, 2019 at 10:45 AM Jonas Devlieghere <jonas at devlieghere.com> wrote: > Hi Kostya, > > I remember seeing this in the past. IIRC it was sufficient to install > recommonmark with `pip install recommonmark`. > installing this on my machine won't help the bots that build the docs, right? > > Cheers, > Jonas > > On Tue, Feb 12, 2019 at 10:17 AM

Hi, TL;DR - We should update the bot(s) responsible for building the LLVM documentation so that they use recommonmark 0.5.0, and apply https://reviews.llvm.org/D63211. Full context: I recently started trying to build the sphinx docs. However, a change by Jordan (r363100) resulted in me no longer being able to build them, even though the build bots were green and he could build them himself.

Hi, docs seem to be broken. e.g. r353563 adds docs for callbr, but https://llvm.org/docs/LangRef.html doesn't have it. trying to build the docs manually on my box: ninja docs-llvm-html FAILED: docs/CMakeFiles/docs-llvm-html cd /usr/local/google/home/kcc/llvm-build/docs && /usr/bin/sphinx-build -b html -d /usr/local/google/home/kcc/llvm-build/docs/_doctrees-llvm-html -q -W

Hi, Thanks for bringing this up. I am reluctant to update to recommonmark >= 0.4.0, because it is not available in any Ubuntu version, Debian Testing or even Debian Unstable. While we could do something custom on the buildbot, I think it would be a disservice for our users to use a library that is not packaged in modern operating systems yet. Dmitri

On Tue, Feb 12, 2019 at 11:05 AM Jonas Devlieghere via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On Tue, Feb 12, 2019 at 10:54 AM Kostya Serebryany <kcc at google.com> wrote: > >> >> >> On Tue, Feb 12, 2019 at 10:45 AM Jonas Devlieghere <jonas at devlieghere.com> >> wrote: >> >>> Hi Kostya, >>> >>> I remember

There's been some desire recently to start writing documentation in Markdown instead of reStructuredText. I put up a [patch]( https://reviews.llvm.org/D44910) for that, but we should figure out a policy on how we want our documentation written first. The desire to use Markdown comes mostly from it being simpler, and having much wider adoption. It does lack some of the feature that

If Sphinx consumes Markdown, great, let's do it. We can migrate docs from .rst to .md easily over time. On Thu, Mar 29, 2018 at 1:26 PM Michael Spencer via llvm-dev < llvm-dev at lists.llvm.org> wrote: > There's been some desire recently to start writing documentation in > Markdown instead of reStructuredText. I put up a [patch]( > https://reviews.llvm.org/D44910) for

Agreed.  Markdown is also nice for the github integration.  It might make some of our docs more easily discoverable.  (and maybe editable someday) On 03/29/2018 01:34 PM, Reid Kleckner via llvm-dev wrote: > If Sphinx consumes Markdown, great, let's do it. > > We can migrate docs from .rst to .md easily over time. > > On Thu, Mar 29, 2018 at 1:26 PM Michael Spencer via

+1, using Markdown should reduce the friction in asking people to write LLVM docs. On Thu, Mar 29, 2018 at 1:42 PM Philip Reames via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Agreed. Markdown is also nice for the github integration. It might make > some of our docs more easily discoverable. (and maybe editable someday) > > On 03/29/2018 01:34 PM, Reid Kleckner via

Last night, I triggered a buildbot error after my most recent commit. That one was totally on me as the warning did pop up while generating the docs site locally using the sphinx-build command (confirmed this afternoon). I just checked in a commit to resolve the error but now it appears I've triggered a different buildbot error? This error did not come up when I built the site locally to test

On 08/01/2018 19:16, Matthias Braun wrote: > I believe the results of the docu generation can be found here: > > http://lists.llvm.org/pipermail/www-scripts/2018-January/thread.html > > (though a nice improvement for the future would be to make this into a > buildbot or jenkins job so people would get direct blame mails) > Thanks Matthias. I had a look at the error

I followed the lnt quickstart <http://llvm.org/docs/lnt/quickstart.html> directions but got this diagnostic when doing the setup: bash-3.2$ ~/mysandbox/bin/python ~/lnt/setup.py develop /Users/dcallahan/mysandbox/lib/python2.7/site-packages/setuptools/dist.py:284: UserWarning: The version spec\ ified requires normalization, consider using '0.4.1.dev0' instead of

On Fri, Mar 30, 2018 at 1:56 AM, David Chisnall <theraven at theravensnest.org> wrote: > On 29 Mar 2018, at 21:25, Michael Spencer via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > > > There's been some desire recently to start writing documentation in > Markdown instead of reStructuredText. I put up a [patch]( > https://reviews.llvm.org/D44910) for

On Tue, Aug 20, 2019 at 9:25 PM Michael Spencer via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On Mon, Aug 19, 2019 at 12:38 PM via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> Hi everyone. My name is DeForest Richards. I’m the technical writer who was selected to work on the LLVM project as part of the Google Season of Docs program. I’ll be helping to

Hi, I am new to llvm with a particular interested in the optimization area, specially on SLP. While working through the tutorial, I ran this example [1] with the hope to see SLP vectorization in action but for some reason, I do not see it on the LLVM assembly as seen below. Is there anything I am missing? I am using Clearlinux as build machine and this has clang version 9.0.0.

I will get this fixed today. Sorry I have been dealing with some family stuff yesterday. -Tanya > On Jan 9, 2018, at 9:58 AM, Florian Hahn <florian.hahn at arm.com> wrote: > > > >> On 08/01/2018 19:16, Matthias Braun wrote: >> I believe the results of the docu generation can be found here: >>

Hi David, That's weird, I have setup LNT in multiple different distros and have never seen this. Looks like no one ever tested on the system you're running. Can you share a bit more of your environment? Also, you can check the setup.py to see if it does any stripping of package names, which could go wrong in the wrong environment. cheers, --renato On 29 January 2015 at 20:13, David

Pyxml/xmlproc is being used in tools/xen/xm/xenapi_create.py but is unmaintained for several years now. xmlproc is used only for validating XML documents against a DTD file. This patch replaces the pyxml/xmlproc based XML validation with code based on lxml, which is actively maintained. Signed-off-by: Stephan Peijnik <spe@anexia.at> diff -r 6e0ffcd2d9e0 -r 7082ce86e492

I am sure quite a number of packages not supported in the distribution are easy to build and install into /usr/local/bin and such. It is not that it is easy to defeat the standard distribution and update procedures as that doing so puts that software out of sync with the standard update procedure. From then on the distribution update for cmake has no effect. I suspect there are fairly rigid

I believe the results of the docu generation can be found here: http://lists.llvm.org/pipermail/www-scripts/2018-January/thread.html <http://lists.llvm.org/pipermail/www-scripts/2018-January/thread.html> (though a nice improvement for the future would be to make this into a buildbot or jenkins job so people would get direct blame mails) - Matthias > On Jan 8, 2018, at 10:27 AM,