search for: metabug

...5, at 05:30, Alex Bradbury via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> * LLVM's autoconf-based build system is now officially deprecated, with the >> CMake build system being preferred. >> [r252520](http://reviews.llvm.org/rL252520). > > Is there a metabug in bugzilla that is tracking bugs that are blocking transition to using cmake? Or is there some other way that packagers can indicate issues that should be addressed before the autoconf build system is removed? > > eg: https://llvm.org/bugs/show_bug.cgi?id=19465 Chris Bieneman has been post...

...uses the first: > z <- cbind( c(NA,NA), c(NA,NaN), c(NaN,NA), c(NaN,NaN)) > rowsum(z, c("a","a")) [,1] [,2] [,3] [,4] a NA NaN NA NaN > z[1,,drop=FALSE] + z[2,,drop=FALSE] [,1] [,2] [,3] [,4] [1,] NA NA NaN NaN (The name rowsum is a metabug, since it may be confused with the entirely different rowSums, but it has been around for a long time.) Bill Dunlap Spotfire, TIBCO Software wdunlap tibco.com

Jeremy, At this point the belief is that there are no issues left blocking removing autoconf. The plan is to remove it after the 3.8 branch. In case you missed the thread where that was decided it is here (http://lists.llvm.org/pipermail/llvm-dev/2015-November/092150.html <http://lists.llvm.org/pipermail/llvm-dev/2015-November/092150.html>). This discussion has been going on for over a

...process. 3. Commit the new git-llvm script directly to github. 4. Grant all contributors write access to the repository. 5. Email lists announcing that the migration is complete. Once the migration is complete, if you run into any issues, please file a bug, and mark it as a blocker for the github metabug PR39393. If you have any questions or think I am missing something, please let me know. Thanks, Tom

...(S-Plus) who moved it to global status. That is, they used it in enough other places that they decided to speed it up, took over the maintainance and ownership of the function (with my blessing), and ceased to label it as part of "survival" in the manual. This "metabug" can't be laid at R's feet. Terry Therneau

...how_bug.cgi?id=181 May require to modify many LOCs, but should be pretty easy to do. * The doc about the command line arguments and the config file is out of date. See TextCP, XVideoPort and Synchronous for instance. I'm sure there are plenty of other things that are out of date. * Metabug: Test Wine with the VXCL samples #242: http://wine.codeweavers.com/bugzilla/show_bug.cgi?id=242 Get the VXCL samples, test them with Wine and report the bugs in the bugzilla database. I know there's lots of them. Then people (or yourself) can start fixing these bugs in a distributed...

Dear all, My name is Mohamed and I am a first year computer science masters student. I am writing this email because I am interested in the project idea "Debug Info Should have no effect on codegen". So far I have built llvm and clang and I was trying to reproduce the problem on simple c++ programs but I can't. Being specific this are the steps I am doing: $ clang -g test.cc > $

...uests to bugzilla. It's recommend that you use this script in order to give us consistent bugzilla entries. However, you can still file bugzilla requests manually if for some reason you are unable to use the script. If you file bugs manually, make sure you mark it as a blocker for the release metabug: 32061 and add a link the commit on phabricator in the url field: e.g http://reviews.llvm.org/rL12345 Description for the bug should be in the form of: Merge r123456 into the 4.0 branch : <80 character commit message summary> * Stable Release Improvements * I would like to start an infor...

...t we can handle this and other potential restrictions in the future? - Tom > > > 5. Email lists announcing that the migration is complete. > > Once the migration is complete, if you run into any issues, please file > a bug, and mark it as a blocker for the github metabug PR39393. > > If you have any questions or think I am missing something, please > let me know. > > > This is fantastic! Thank you so much for doing this work Tom :) > > -- > Mehdi > >

LLVM Weekly - #98, Nov 16th 2015 ================================ If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/98>. Welcome to the ninety-eighth issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by [Alex Bradbury](http://asbradbury.org).

On 12/15/11 11:15 AM, Duncan Sands wrote: > Hi Ping, > >> Is there any method to compile linux-2.6 with llvm-gcc? I google the >> information, but found nothing. Can anybody help me? > llvm-2.6 is so old I doubt anyone here wants to think about it. > But why do you want to compile LLVM with llvm-gcc? Just compile > it with gcc or whatever compiler you have to hand.

Hi Hans, 2016-07-30 0:57 GMT+02:00 Hans Wennborg via llvm-dev <llvm-dev at lists.llvm.org>: > There are still open merge requests and bugs, but I'd like to get the > real testing started to see where we're at. Just to double-check, is this bug also on people's radar? It causes Clang to crash when trying to build a fair number of Open Source packages/libraries. In my

...ure? > > - Tom > > > > > > 5. Email lists announcing that the migration is complete. > > > > Once the migration is complete, if you run into any issues, please file > > a bug, and mark it as a blocker for the github metabug PR39393. > > > > If you have any questions or think I am missing something, please > > let me know. > > > > > > This is fantastic! Thank you so much for doing this work Tom :) > > > > -- > > Mehdi >...

...> >> > > 5. Email lists announcing that the migration is complete. >> > > >> > > Once the migration is complete, if you run into any issues, >> please file >> > > a bug, and mark it as a blocker for the github metabug >> PR39393. >> > > >> > > If you have any questions or think I am missing something, >> please >> > > let me know. >> > > >> > > >> > > This is fantastic! Thank you so much for doing...

...you use this script in order to give us consistent bugzilla entries. >> However, you can still file bugzilla requests manually if for some >> reason you are unable to use the script. >> >> If you file bugs manually, make sure you mark it as a blocker for >> the release metabug: 32061 and add a link the commit on phabricator >> in the url field: e.g http://reviews.llvm.org/rL12345 >> >> Description for the bug should be in the form of: >> >> Merge r123456 into the 4.0 branch : <80 character commit message summary> >> >> >...

Dear testers, 3.9.0-rc1 was just tagged from the 3.9 branch at r277207. This took a little longer than I'd hoped, but I think the branch is in a decent state now. There are still open merge requests and bugs, but I'd like to get the real testing started to see where we're at. Please build, test, and upload binaries to the sftp. Let me know how it goes. I'll upload source, docs,

...e 5243 Hyperlobby: runtime error 430 5423 AOL AIM won't install: complains about minimum requirements 6496 Defcon crashes in ws2_32 7026 Formula objects in Word 97 always trigger unhandled page fault 7598 Regedit cannot import/export version 5 registry files 7600 Regedit Metabug: get regedit working perfectly 7670 No battle sounds in Guild Wars 7851 Warrock installer crash 8674 Safari crashes on startup 8763 Evernote crashes 9014 MS Office 2007 Home and Student edition installer crashes 9364 Call from 0x7b840a80 to unimplemented function gdiplus.dll...