similar to: [LLVMdev] Python version requirement for LLVM

On Wed, Jun 25, 2014 at 5:52 PM, Gregory Szorc <gregory.szorc at gmail.com> wrote: > As much as I like killing support for Python 2.6 and below, RHEL is > usually the blocker. They still have 2.4 under support. Only the RHEL that > was released a few weeks ago finally has 2.7. > Given the amount of complexity required to build LLVM & Clang (having the right compiler &

Yes, I am working on it. The sub-projects are still having issues but the other documentation has been fixed. -Tanya > On Feb 14, 2019, at 3:53 AM, Alexander Kornienko <alexfh at google.com> wrote: > > Tanya, friendly ping. > > On Mon, Feb 11, 2019 at 3:21 PM Alexander Kornienko <alexfh at google.com <mailto:alexfh at google.com>> wrote: > Hi Tanya, >

Ping. On Fri, Jul 27, 2012 at 3:42 AM, Alexander Kornienko <alexfh at google.com>wrote: > On Fri, Jul 27, 2012 at 2:02 AM, Richard Smith <richard at metafoo.co.uk>wrote: > >> On Thu, Jul 26, 2012 at 4:24 PM, Jim Grosbach <grosbach at apple.com> wrote: >> >>> >>> On Jul 26, 2012, at 4:07 PM, Chris Lattner <clattner at apple.com> wrote:

While you're here, Xenial (15.10) seems wrong (should be 16.04 LTS). On Wed, Apr 27, 2016 at 12:32 PM, Sylvestre Ledru <sylvestre at debian.org> wrote: > Hello > > Indeed, this package no longer exists. I removed it from llvm.org/apt/ > > Thanks, > Sylvestre > > Le 27/04/2016 à 12:23, Alexander Kornienko a écrit : > > Adding Sylvestre, who should know how

Ping. On Thu, Aug 9, 2012 at 3:04 PM, Alexander Kornienko <alexfh at google.com>wrote: > Ping. > > > On Fri, Jul 27, 2012 at 3:42 AM, Alexander Kornienko <alexfh at google.com>wrote: > >> On Fri, Jul 27, 2012 at 2:02 AM, Richard Smith <richard at metafoo.co.uk>wrote: >> >>> On Thu, Jul 26, 2012 at 4:24 PM, Jim Grosbach <grosbach at

Thanks, I fixed the typo with Xenial. I don't know if I want to bring back llvm-jenkins.d.n again yet. if people see an interest in it, why not :) Le 27/04/2016 à 13:06, Alexander Kornienko a écrit : > ... and http://llvm-jenkins.debian.net/ seems to be down. Sorry for > bugging you with all of this, and thanks for fixing the > clang-modernize thingy so quickly! > > On Wed,

Thank you! It seems like new changes in .rst files are picked up quickly now. -- Alex On Thu, Feb 14, 2019 at 7:33 PM Tanya Lattner <tonic at nondot.org> wrote: > This should all be fixed now. > > Thanks, > Tanya > > > On Feb 14, 2019, at 9:50 AM, Tanya Lattner <tonic at nondot.org> wrote: > > Yes, I am working on it. The sub-projects are still having

On Fri, Jul 27, 2012 at 2:02 AM, Richard Smith <richard at metafoo.co.uk>wrote: > On Thu, Jul 26, 2012 at 4:24 PM, Jim Grosbach <grosbach at apple.com> wrote: > >> >> On Jul 26, 2012, at 4:07 PM, Chris Lattner <clattner at apple.com> wrote: >> >> > <dropping llvm-commits> >> > >> > On Jul 2, 2012, at 9:59 AM, Alexander

Adding Sylvestre, who should know how to fix that. On Tue, Apr 26, 2016 at 10:39 PM, Nick Wiggill <nick.wiggill at gmail.com> wrote: > Thanks for your replies, gentlemen. I'm in good standing with my install, > then. > > On the apt page <http://llvm.org/apt/>, it should not be suggested then > to "apt-get install [..etc..] clang-modernize-3.8 [..etc..]"

Hi Tanya, Last time I noticed a problem with clang-tools-extra docs you could help solving them. If someone else is taking care of this part of the infrastructure now, please redirect appropriately. It looks like docs generated from rst (for LLVM, Clang and clang-tools-extra) don't get updated at the moment. They stopped updating somewhere between r353327

Hi llvmdev, llvm-commits, There was a discussion on this topic a while ago, and now I've decided to make a formal proposal and post it here. I propose to add the LLVM_FALLTHROUGH macro for specifying intended fall-through locations between switch cases. *INTRODUCTION* The switch construct of C/C++ languages allows fall-throughs between switch labels when control flow is not directed

The docs are in a good shape in this regard: http://clang.llvm.org/extra/clang-modernize.html http://llvm.org/releases/3.8.0/tools/clang/tools/extra/docs/clang-modernize.html Apparently, it doesn't make the fact more discoverable though. On Tue, Apr 26, 2016 at 11:27 AM, Benjamin Kramer via llvm-dev < llvm-dev at lists.llvm.org> wrote: > clang-modernize was folded into clang-tidy

I've started using YAML I/O in clang-format configuration parser, and stumbled upon a bug with handling empty input string. While filing it ( http://llvm.org/bugs/show_bug.cgi?id=15927), I've found another bug which hasn't been answered to since March ( http://llvm.org/bugs/show_bug.cgi?id=15505). So, the question is: how ready is YAML I/O ready for using in production code? Thanks!

On Sunday, I did a "yum update" which installed kernel 2.6.32-573.3.1.el6.i686 on half a dozen virtual machines running CentOS 6.7. Since then, two of them have gone into "meltdown", and started spewing "ABRT Daemon" emails: one on Tuesday, and one tonight. The machines have a very light workload -- one runs "trac", and a handful of development systems,

Hello Chris, We're using LLVM CommandLine 2.0 Library in the clang-check tool. Overall it works fine for us, but there are a couple of problems related to the library design and current usage patterns. First, there's a feature<http://llvm.org/docs/CommandLine.html#exploiting-external-storage> : *"Several of the LLVM libraries define static cl::opt instances that will

Ultimately, I'd like to add a unit test covering our recent fix for handling globals from consecutive -c, but let's start with a simple test that --help output is sane. Sanity includes a mention of the man page for more details (similar to nbdkit --help, although I couldn't figure out how to make python's argparse output that sentence last). --- python/nbdsh.py | 3 ++-

On Tue, 1 Sep 2020 at 18:59, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > On Tue, Sep 1, 2020 at 9:10 AM Analabha Roy <hariseldon99 at gmail.com> > wrote: > > Any suggestions on how to trace the config issues? Do I have to debug > the va_openDriver() function? > > My guess, without reading any code, is that DRI_PRIME isn't doing what > you want it to, and

There was some talk on IRC last week about desire for Python bindings to LLVM's Object.h C interface. So, I coded up some and you can now find some Python bindings in trunk at bindings/python. Currently, the interfaces for Object.h and Disassembler.h are implemented. I'd like to stress that things are still rough around the edges, so use at your own risk. I intend to smooth things over in

This is Chris' call to make, imo. -j On Aug 22, 2012, at 3:59 PM, Alexander Kornienko <alexfh at google.com> wrote: > Ping. > > On Thu, Aug 9, 2012 at 3:04 PM, Alexander Kornienko <alexfh at google.com> wrote: > Ping. > > > On Fri, Jul 27, 2012 at 3:42 AM, Alexander Kornienko <alexfh at google.com> wrote: > On Fri, Jul 27, 2012 at 2:02 AM, Richard

I'd like to continue the discussion about minimum Python versions from the "Use multiprocessing instead of threading" thread in its own thread because I feel it warrants additional discussion. In that thread, we were discussing maintaining support for Python 2.4 and 2.5. The latest response is: On Fri, Nov 30, 2012 at 1:40 PM, Daniel Dunbar <daniel at zuster.org> wrote: >