similar to: [LLVMdev] Command Line Bugzilla

I don't know the answer to this question, but I've attached an (old) version of pybugz that I tweaked a little to work with LLVM bugzilla. You can probably write such queries on top of this if you feel like figuring out its API: -- $ ./bugz get -n 1000 * Using http://llvm.org/bugs/ * Getting bug 1000 .. Title : Chris Is Buggy Assignee : tonic Reported : 2006-11-10

On Thu, Nov 7, 2013 at 4:58 PM, Daniel Dunbar <daniel at zuster.org> wrote: > I don't know the answer to this question, but I've attached an (old) > version of pybugz that I tweaked a little to work with LLVM bugzilla. You > can probably write such queries on top of this if you feel like figuring > out its API: > Thanks. Looks like most of the pages have some way to

On 08/11/2013 05:56, Sean Silva wrote: > > > > On Thu, Nov 7, 2013 at 4:58 PM, Daniel Dunbar <daniel at zuster.org > <mailto:daniel at zuster.org>> wrote: > > I don't know the answer to this question, but I've attached an > (old) version of pybugz that I tweaked a little to work with LLVM > bugzilla. You can probably write such queries on

Does anybody know if we have bugzilla's REST API enabled, and if so how to access it? <https://wiki.mozilla.org/Bugzilla:REST_API:Methods>. I tried e.g. http://llvm.org/bugs/bug/count but there doesn't seem to be anything there. I'd like to write a script that tracks various statistics e.g. how many bugs were filed in the last week, how many were closed, etc. and a REST API

On Feb 25, 2011, at 11:38 AM, Rafael Avila de Espindola wrote: >>> Can someone else try to reproduce this? > > I tried gcc.c from > http://people.csail.mit.edu/smcc/projects/single-file-programs/ and the > difference is a bit more noticeable: > > -O0 -mno-relax-all > > real 0m13.182s > user 0m12.690s > sys 0m0.450s > > -O0 > > gcc.o is

>> Can someone else try to reproduce this? I tried gcc.c from http://people.csail.mit.edu/smcc/projects/single-file-programs/ and the difference is a bit more noticeable: -O0 -mno-relax-all real 0m13.182s user 0m12.690s sys 0m0.450s -O0 gcc.o is 10932968 bytes. real 0m12.969s user 0m12.520s sys 0m0.410s gcc.o is 11410552 bytes IMHO it would still be reasonable to switch to

Nice! This looks good to me but probably Chris or someone else should sign off on it. There were two minor warnings on Darwin: -- In file included from /Volumes/Data/Users/ddunbar/llvm/lib/Support/regexec.c:81: /Volumes/Data/Users/ddunbar/llvm/lib/Support/regengine.inc: In function 'sbackref': /Volumes/Data/Users/ddunbar/llvm/lib/Support/regengine.inc:665: warning: control reaches end of

Hi Daniel! Daniel Dunbar wrote: > I merged in my changes to your patch, which results in the attached > patch. There may be some missed merge errors. The main problem I have > with the rest of this patch is that it causes a regression in > llvm-prof's behavior. I tried running edge profiling on the > MultiSource/Applications/aha benchmark in the llvm test-suite, and >

Hi Andreas, Sorry for the lag time... On Wed, Jul 22, 2009 at 5:47 AM, Andreas Neustifter<e0325716 at student.tuwien.ac.at> wrote: > Hi Daniel! > > Daniel Dunbar wrote: >> I merged in my changes to your patch, which results in the attached >> patch. There may be some missed merge errors. The main problem I have >> with the rest of this patch is that it causes a

Good Morning. On 22.07.09 14:47), Andreas Neustifter wrote: > Daniel Dunbar wrote: >> I merged in my changes to your patch, which results in the attached >> patch. There may be some missed merge errors. The main problem I have >> with the rest of this patch is that it causes a regression in >> llvm-prof's behavior. I tried running edge profiling on the >>

Sorry, forgot attachment. On 23.07.09 07:40), Andreas Neustifter wrote: > Good Morning. > > On 22.07.09 14:47), Andreas Neustifter wrote: >> Daniel Dunbar wrote: >>> I merged in my changes to your patch, which results in the attached >>> patch. There may be some missed merge errors. The main problem I have >>> with the rest of this patch is that it

Hi! Daniel Dunbar wrote: > > Sorry for the lag time... No problem. As long as I know that you get to it sometime its fine for me... > On Wed, Jul 22, 2009 at 5:47 AM, Andreas > Neustifter<e0325716 at student.tuwien.ac.at> wrote: >> Hi Daniel! >> >> Daniel Dunbar wrote: >>> I merged in my changes to your patch, which results in the attached

Hi Andreas, Thanks for breaking things up. I applied two pieces of this patch in separate no-functionality-change commits, here: http://llvm.org/viewvc/llvm-project?view=rev&revision=75623 and here: http://llvm.org/viewvc/llvm-project?view=rev&revision=75625 I merged in my changes to your patch, which results in the attached patch. There may be some missed merge errors. The main

On Tue, Dec 10, 2013 at 9:46 AM, Alp Toker <alp at nuanti.com> wrote: > > On 08/11/2013 05:56, Sean Silva wrote: > > >> >> >> On Thu, Nov 7, 2013 at 4:58 PM, Daniel Dunbar <daniel at zuster.org <mailto: >> daniel at zuster.org>> wrote: >> >> I don't know the answer to this question, but I've attached an >>

Hi, I am currently trying to set up new performance and regression testers for Polly and LLVM and would like to XFAIL two test cases. I am using the LNTBuilder instead of the NightlyTestBuilder out of the assumption that the LNTBuilder is the more modern solution. However, when trying to xfail test cases I realized the xfail=[] parameter of getLNTFactor is ignored. Previously this was not an

Hi all, I ran some gcov numbers today for LLVM/clang on their respective test suites (on Darwin/i386). If you are interested, the results are here: http://t1.minormatter.com/~ddunbar/llvm-cov/ and here: http://t1.minormatter.com/~ddunbar/llvm-cov/clang.html High level summary is LLVM's test suite is at 70% line coverage (and that is only the tools that are run) and clang is at 80%. -

https://bugzilla.netfilter.org/show_bug.cgi?id=1210 Bug ID: 1210 Summary: nftables gets confused by user namespaces when meta skuid is used Product: nftables Version: unspecified Hardware: All OS: All Status: NEW Severity: critical Priority: P5 Component: nft

I'm going to bugz this if no one tells me I made another brain-damaged error here. Also, if I can get one confirmation, it'll let me breath easier. I ran a version searching for ".cmd" and ".c" just trying to convince myself I'm not *that* brain-damaged. You'd think after all these years that regex compilation would be pretty darn stable... Oh! Forgot it was

So, I just tried, and basically it's difficult to make progress due to the print statements (since they induce an immediate syntax error). Since 2.4 doesn't support `from __future__ import print_function`, the only alternative I guess is shimming in a print function. This is a maintenance effort that I don't want to do right now (and, TBQH, I feel that the proper maintainer should be

On Jul 11, 2010, at 11:55 AM, Matt Fleming wrote: > On Sun, 11 Jul 2010 10:15:52 -0500, innate one <innate1 at gmail.com> wrote: >> Ping = repost to thread if no feedback given below criteria > > Heh, I think you misunderstood my reply ;-) > > I understand what 'ping' means, I was simply asking Daniel if he has had > chance to deal with this yet. Daniel