similar to: [LLVMdev] Letter-spacing in Sphinx CSS?

Looking through the history with git, it looks like it was just grandfathered in from the original template that the current template is based off of. I don't think that it is going to hurt to remove it. Also, another problem with the current CSS is that some of the different heading types (IIRC in particular <h2> and <h3>) are very difficult to distinguish, which makes some

On Sat, Sep 29, 2012 at 12:29 PM, Sean Silva <silvas at purdue.edu> wrote: > Looking through the history with git, it looks like it was just > grandfathered in from the original template that the current template > is based off of. I don't think that it is going to hurt to remove it. > > Also, another problem with the current CSS is that some of the > different heading

Sean and Michael, Thank you for looking at this. I removed letter-spacing in r164921. The h2/h3 issue could be resolved by making the h2 font slightly bigger. Or we could try to copy Wikipedia's approach by using different formatting for different levels (for example, we could remove the background rectangle from h3 and lower, but instead make them bold). Dmitri --

Hi Eric, On 20 July 2015 at 10:41, Eric Fiselier <eric at efcs.ca> wrote: > Hi All, > > I'm working on rewriting libc++'s documentation using Sphinx. > Hopefully it will be easier to write and maintain documentation using > restructured text and not HTML. > > What steps do I need to take to get libc++ a Sphinx builder and get > the required changes made for

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 Fri, Jul 31, 2015 at 12:01 AM, Dan Liew <dan at su-root.co.uk> wrote: > Hi Eric, > > On 20 July 2015 at 10:41, Eric Fiselier <eric at efcs.ca> wrote: >> Hi All, >> >> I'm working on rewriting libc++'s documentation using Sphinx. >> Hopefully it will be easier to write and maintain documentation using >> restructured text and not HTML.

Hi All, I'm working on rewriting libc++'s documentation using Sphinx. Hopefully it will be easier to write and maintain documentation using restructured text and not HTML. What steps do I need to take to get libc++ a Sphinx builder and get the required changes made for libcxx.llvm.org? /Eric

Hello, All LLVM HTML documents have been converted to reST. This uncovered an issue with 'make install', which installs only *.html files and completely ignores *.rst (it does not invoke Sphinx to process reST). In order to unbreak 'make install', I checked in a Dummy.html file in r170126 to allow 'make install' to proceed. We need some way to integrate normal 'make

On Thu, Jan 17, 2013 at 1:19 AM, Dmitri Gribenko <gribozavr at gmail.com> wrote: > On Wed, Jan 16, 2013 at 9:33 PM, Dmitri Gribenko <gribozavr at gmail.com> wrote: >> On Wed, Jan 16, 2013 at 9:24 PM, Chris Lattner <clattner at apple.com> wrote: >>> >>> On Jan 16, 2013, at 10:32 AM, Dmitri Gribenko <gribozavr at gmail.com> wrote: >>>

Hello, JFYI so that no work will be duplicated. My colleagues and I will take care of converting the rest of the documentation to rst. Dmitri -- main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i%j)){j=0;break;}}if (j){printf("%d\n",i);}}} /*Dmitri Gribenko <gribozavr at gmail.com>*/

On Thu, Jan 17, 2013 at 1:23 AM, Evgeniy Stepanov <eugeni.stepanov at gmail.com> wrote: > On Thu, Jan 17, 2013 at 1:19 AM, Dmitri Gribenko <gribozavr at gmail.com> wrote: >> On Wed, Jan 16, 2013 at 9:33 PM, Dmitri Gribenko <gribozavr at gmail.com> wrote: >>> On Wed, Jan 16, 2013 at 9:24 PM, Chris Lattner <clattner at apple.com> wrote: >>>>

It wouldn't take me more than an hour or two to do the format conversion. It is rather trivial, actually. Just say the word and I'm on to it like a starving bee. I guess I should get used to using the Sphinx layout; I'm simply more familiar with the format I use on my own websites. Have you guys ever considered making a less formal wiki for LLVM documentation - a place where tiny

On Wed, Jan 16, 2013 at 9:24 PM, Chris Lattner <clattner at apple.com> wrote: > > On Jan 16, 2013, at 10:32 AM, Dmitri Gribenko <gribozavr at gmail.com> wrote: > >> Hello, >> >> When someone breaks a FileCheck-based test on some buildbot, sometimes >> it may not be obvious *why* did it fail. If the failure can not be >> reproduced locally, it can

Note that as far as places to put temporary files, the right place to put them is alongside the other test outputs in the test output "sandbox" directory. Somewhat orthogonal, but we should also fix up lit to purge those sandboxes before it starts a new test run. - Daniel On Wed, Jan 16, 2013 at 3:31 PM, Dmitri Gribenko <gribozavr at gmail.com>wrote: > On Thu, Jan 17, 2013

On Thu, Jan 17, 2013 at 8:36 AM, Dmitri Gribenko <gribozavr at gmail.com> wrote: > We have to options: > (a) replace 'FileCheck' with '%FileCheck' in all tests, and teach > 'lit' to replace '%FileCheck' with 'FileCheck --dump-input-on-error'; > > (b) teach 'lit' to replace a plain 'FileCheck'. > > The first approach

Hi, I have istalled LLVM 3.1 Release+Asserts build. I was just trying out the hello world sequence of steps in the installation instructions. However when I run lli or llvm-dis I get an error "invalid MODULE_CODE_GLOBALVAR record". I have searched the web and I am not able to fathom what the problem and its fix is. I have GCC 4.6.3 running on a Ubuntu 12.04 LTS x86-64. Please let me

On Tue, Jan 21, 2014 at 10:20 AM, Dmitri Gribenko <gribozavr at gmail.com>wrote: > On Tue, Jan 21, 2014 at 8:03 PM, Renato Golin <renato.golin at linaro.org> > wrote: > > Chandler, > > > > I may be doing this wrong, but I'm getting a weird error in building LLVM > > with Clang via CMake. > > I have been debugging a similar issue that I isolated

On Thu, Jan 17, 2013 at 3:31 AM, Dmitri Gribenko <gribozavr at gmail.com> wrote: > On Thu, Jan 17, 2013 at 1:23 AM, Evgeniy Stepanov > <eugeni.stepanov at gmail.com> wrote: >> On Thu, Jan 17, 2013 at 1:19 AM, Dmitri Gribenko <gribozavr at gmail.com> wrote: >>> On Wed, Jan 16, 2013 at 9:33 PM, Dmitri Gribenko <gribozavr at gmail.com> wrote:

Hello, This came up on IRC in context of r173842, and it was suggested to codify this unspoken rule. Current practice is not to use 'inline' in: class Foo { public: inline void bar() { // ... } }; Dmitri -- main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i%j)){j=0;break;}}if (j){printf("%d\n",i);}}} /*Dmitri Gribenko <gribozavr at gmail.com>*/

Dmitri Gribenko <gribozavr at gmail.com> writes: > Also, you don't need to do a 2-step bootstrap to catch warnings from > gcc. You also don't need a debug build, just an optimized one -- > since it is faster to link, and gcc emits more warnings when > optimization is no. Actually, there are cases a debug build catches that an optimized build doesn't because