similar to: IMPORTANT: *.llvm.org certificates being renewed (impacts SVN) FRIDAY Sept 22

All, The following websites will be moving to a new web server in the next few days: clang.llvm.org <http://clang.llvm.org/> clang-analyzer.llvm.org <http://clang-analyzer.llvm.org/> compiler-rt.llvm.org <http://compiler-rt.llvm.org/> dragonegg.llvm.org <http://dragonegg.llvm.org/> klee.llvm.org <http://klee.llvm.org/> libclc.llvm.org <http://libclc.llvm.org/>

On 03/20/2017 03:33 PM, Jonathan Roelofs wrote: > On 3/20/17 1:47 PM, Evandro Menezes via llvm-dev wrote: >> Folks, >> >> I'm at a loss trying to add Compiler-RT to an LLVM build, even after >> checking out the instructions at http://compiler-rt.llvm.org, so I'd >> appreciate your help. >> >> I've tried adding the CMake options

On 10/11/2018 03:27 PM, James Y Knight via llvm-dev wrote: > TLDR: https://github.com/llvm-git-prototype/ exists as a read-only mirror of SVN, and is being updated continuously with a script running on an llvm-project AWS VM. > Hi James, What is the current status of the monorepo, have you resolved all the known issues with the history? Are there any other changes that need to be made

Hi Nelson, Thanks for your reply. The “build/Debug/lib” and "build/Release/lib” directories is where all the libraries go. Similarly, the executables go to “build/Debug/bin” and “build/Release/bin” before they are moved to the install directory. This is expected and normal. However, the problem is that a small number of libraries (exactly 20 in total) are not created at all for the LLVM

In prepping our next release, we noticed that the LICENSE.TXT files were still all copyrighted 2015. I've done a bit of archaeology and it looks like the files to update are: cfe/trunk/LICENSE.TXT clang-tools-extra/trunk/LICENSE.TXT compiler-rt/trunk/LICENSE.TXT libclc/trunk/LICENSE.TXT libcxx/trunk/LICENSE.TXT libcxxabi/trunk/LICENSE.TXT lld/trunk/LICENSE.TXT llvm/trunk/LICENSE.TXT

> On Mar 30, 2016, at 1:57 PM, Robinson, Paul via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > In prepping our next release, we noticed that the LICENSE.TXT files > were still all copyrighted 2015. I've done a bit of archaeology and > it looks like the files to update are: > > cfe/trunk/LICENSE.TXT > clang-tools-extra/trunk/LICENSE.TXT >

On Fri, Nov 16, 2018 at 4:04 PM NAKAMURA Takumi <geek4civic at gmail.com> wrote: > Hello, David. > > On Sat, Nov 17, 2018 at 7:46 AM David Jones via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> Hi James, >> >> I've started working with the prototype layout in context of Google's >> internal infrastructure. With deep apologies, I

I understand that a difference between ninja and xcode is they use a different way to determine code dependencies. So to my understanding xcode needs dependencies to be properly created whereas ninja just doesn’t care. Maybe this is why ninja is able to find what it needs for the compilation to succeed, but not xcode. So I have now looked at the CMakeLists.txt files and found that all the missing

Hello everyone, Below are some buildbot numbers for the last week of 5/22/2016 - 5/28/2016. Thanks Galina "Status change ratio" by active builder (percent of builds that changed the builder status from greed to red or from red to green): buildername | builds | changes | status change ratio

Hello everyone, Below are some buildbot numbers for the week of 4/22/2018 - 4/28/2018. Please see the same data in attached csv files: The longest time each builder was red during the week; "Status change ratio" by active builder (percent of builds that changed the builder status from greed to red or from red to green); Count of commits by project; Number of completed builds, failed

Try using ninja generator, most people do not use Xcode for building, so since it lesser-used, it also lesser tested. Note that it’s perfectly possible to use Xcode for code browsing, debugging, editing while using ninja for building, which is what I think most people do On Sun, Jul 7, 2019 at 4:20 AM Joan Lluch via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I also filled a bug

Dear All, Just a reminder that the maintenance will be commencing now. -- John T. John Criswell wrote: > Dear LLVMers and Clangers, > > We'll be doing some maintenance on the LLVM repository on Tuesday, Sept. > 14 (tomorrow). There were some files committed to the repository that > we believe need to be removed from both mainline, the branches, and the > revision

Dear LLVMers and Clangers, We'll be doing some maintenance on the LLVM repository on Tuesday, Sept. 14 (tomorrow). There were some files committed to the repository that we believe need to be removed from both mainline, the branches, and the revision history. The SVN repository will go *off-line* at 7:00 am Central Daylight Savings time on Tuesday. Please do not make any commits after

Hi James, I've started working with the prototype layout in context of Google's internal infrastructure. With deep apologies, I have a (very late, I know) pair of requests that have only recently solidified for me. 1. Could you add annotated tags after the cut point of each release? (I think this would probably be easy.) 2. Could you mark branch/tag operations somehow other than a

Tomorrow evening, community services may have intermittent availability due to maintenance. This maintenance will begin at approximately 6:00 PM CDT[1] and is expected to last only a few minutes and no longer than one(1) hour, ending around 7:00 PM. The affected services are: * All Asterisk community services including everything in the asterisk.org domain. Thank you for your support! [1]:

Hello everyone, Below are some buildbot numbers for the week of 2/25/2018 - 3/03/2018. Please see the same data in attached csv files: The longest time each builder was red during the week; "Status change ratio" by active builder (percent of builds that changed the builder status from greed to red or from red to green); Count of commits by project; Number of completed builds, failed

Hello everyone, Below are some buildbot numbers for the last week of 3/18/2018 - 3/24/2018. Please see the same data in attached csv files: The longest time each builder was red during the week; "Status change ratio" by active builder (percent of builds that changed the builder status from greed to red or from red to green); Count of commits by project; Number of completed builds,

Hello everyone, Below are some buildbot numbers for the week of 1/21/2018 - 1/27/2018. Please see the same data in attached csv files: The longest time each builder was red during the week; "Status change ratio" by active builder (percent of builds that changed the builder status from greed to red or from red to green); Count of commits by project; Number of completed builds, failed

Hello everyone, Below are some buildbot numbers for the week of 5/6/2018 - 5/12/2018. Please see the same data in attached csv files: The longest time each builder was red during the week; "Status change ratio" by active builder (percent of builds that changed the builder status from greed to red or from red to green); Count of commits by project; Number of completed builds, failed

Hello everyone, Below are some buildbot numbers for the week of 4/8/2018 - 4/14/2018. Please see the same data in attached csv files: The longest time each builder was red during the week; "Status change ratio" by active builder (percent of builds that changed the builder status from greed to red or from red to green); Count of commits by project; Number of completed builds, failed