similar to: bot clang-x86-ninja-win7 missing llvm/lib/DebugInfo/MSF/LLVMBuild.txt

The latter. Unfortunately we need to get physical access and delete the checkout. I'm afraid reverting will just reintroduce the problem and re-break all the bots that people already took the time to fix, since going from MSF -> Msf is the same as going from Msf -> MSF On Mon, Aug 1, 2016 at 8:55 AM Reid Kleckner <rnk at google.com> wrote: > So, the MSF rename managed to break

Hi all, If you don't care about Debug Info or PDB files you can stop reading now. Just wanted to give a heads up that I'm planning to add a new folder under DebugInfo called Msf. MSF stands for Multi-Stream File and is the container format used by PDB debug info files. However, MSF by itself is generic enough that it need not contain PDB data, and in fact I can think of at least one

I actually regret doing all caps for PDB, and there seems to be mixed use of all caps / rolling caps even with dwarf (some places say DWARF, others say Dwarf). I don't feel too strongly aside from the minor inconvenience of having to change thousands of occurrences where I already used rolling caps though :-/ On Fri, Jul 22, 2016 at 10:52 AM Reid Kleckner <rnk at google.com> wrote:

Is anyone else seeing.... Updated to revision 277264. Summary of conflicts: Tree conflicts: 2 Tree conflict on 'include/llvm/DebugInfo/Msf' > local dir edit, incoming dir delete or move upon update ... Tree conflict on 'lib/DebugInfo/Msf' > local dir edit, incoming dir delete or move upon update in a 'svn update' on llvm trunk? Strangely these errors

Hi, I've been working on a set of patches to statically link polly in the LLVM tools. There remains an error I can't seem to solve when linking llvm-lto (all other tools luckily get linked correctly): it insists adding libLLVMipo.a after libLLVMPolly.a on the link command, resulting in an error of the form: PassManagerBuilder.cpp:(.text+0x499): undefined reference to

On Thu, Oct 31, 2013 at 12:17 PM, Sebastian Pop <spop at codeaurora.org> wrote: > Is there a reason to not use the cmake add_dependencies to establish the link > order of the LLVM libs instead of using the LLVMBuild.txt info? Have you tried `target_link_libraries`? The new CMake book has an example showing one static lib depending on another (page 25): `target_link_libraries(foo

> -----Original Message----- > From: aaron.ballman at gmail.com [mailto:aaron.ballman at gmail.com] On Behalf > Of Aaron Ballman > Sent: Saturday, July 30, 2016 12:41 PM > To: Robinson, Paul > Cc: Zachary Turner; Sean Silva; Piotr Padlewski; llvm-dev at lists.llvm.org > Subject: Re: [llvm-dev] Upgrading to MSVC 2015 > > On Sat, Jul 30, 2016 at 1:58 PM, Robinson, Paul

I've been experimenting with building various llvm variants on mac OS X. Ususally, it's a case of cloning, running cmake with Xcode as generator and loading the resulting xcodeproj. In trying to build the skeleton openrisc backend from https://github.com/asl/llvm-openrisc as described in "building a backend in 24 hours" at

Hi, I have a CentOS 6.4 fileserver running SerNet Samba 4.0.9 with these global settings (not overridden): read only = No force create mode = 0777 force directory mode = 0777 inherit acls = yes inherit owner = yes inherit permissions = yes On a Windows client, I have Thunderbird 24.0 storing its profile and mail on the Samba share. The

Some background: A while back while working on code to read / write PDB files, I came up with Yet Another Stream Abstraction. Note that LLVM already has a few. Off the top of my head, theres: 1) `MemoryBuffer` and its associated class hierarchy 2) `raw_ostream` and it's associated classes. 3) `DataExtractor` which is used for reading from a StringRef. There's probably more, and

Hi, I have attached a small patch from r192263 that I am using to add LLVM into the toolchain for VS2013. Is someone able to review this and (if all good) submit to the source tree? Changes are all local to llvm/tools/msbuild/ and account for VS2013 requiring the files to be named toolset.props / .targets, rather than the longer name in the previous versions. Cheers, Joshua Samuel

I'm using Windows 8.1, and every time I run check-clang, I eventually end up with a bunch of hung processes. Generally this is an instance of clang.exe, a bunch of instances of FileCheck.exe, and occasionally an llc.exe and an opt.exe. Inside, the processes are all hung inside of calls to WriteFile() attempting to write to stdout. I notice some of the tests fail with output indicating that

On Tue, Jul 26, 2016 at 8:02 AM, Reid Kleckner <rnk at google.com> wrote: > We've been pursuing the direction of writing PDBs from scratch in > llvm/lib/DebugInfo/PDB/Raw and related directories. It might be interesting > to have code that talks to MSPDB140.dll in LLVM, but we really want LLD to > be able to produce its output on any platform. > I completely agree

Hello, Today we hit another VS 2013 breakage < http://lab.llvm.org:8011/builders/sanitizer-windows/builds/26666/steps/run%20tests/logs/stdio> which results us having to alter LLVM. While we have no documented policy of supporting two version of MSVC, we do have an informal agreement that we should support the last two versions. I suggest that we alter our informal policy to the following:

On Tue, Oct 8, 2013 at 7:13 PM, Josh Samuel <JSamuel at iress.com.au> wrote: > I have attached a small patch from r192263 that I am using to add LLVM into > the toolchain for VS2013. > > Is someone able to review this and (if all good) submit to the source tree? I don't have VS2013 to verify this with, but the patch looks good and since it works for you, I've committed

Background is that I have been using Evolution for my MUA for a number of years. Migrated to Evolution from Mozilla Mail. I only use Evolution for email and contacts. Getting bored with the issues (frequently not being able to exit and needing to kill it; Bug Buddy popping up in GNOME, etc) that Mark (MHR) and I and I'm sure others have experienced. About 24 hours ago, I installed

On Wed, Oct 8, 2014 at 12:17 PM, Greg Bedwell <gregbedwell at gmail.com> wrote: > Hi, > > To follow up from Paul last week: > >> I'm expecting to have our internal builds switched over later this >> week. Our investigations have shown no problems. > > We've now updated our internal builds from 2012.4 (cl.exe 17.0.61030) to > 2013.3 (cl.exe

Hi Mike, > I'll check into that again. I ran across llvm-pdbdump earlier but couldn't get it to build on a vanilla 3.8 install (CMake is convinced I don't have the DIA SDK and I haven't found a way to change its mind). I have experienced something similar with the DIA SDK. Most of the time, it is a path problem: https://support.microsoft.com/en-us/kb/3035999

On Mon, Feb 9, 2015 at 8:36 AM, Greg Bedwell <gregbedwell at gmail.com> wrote: > We've just encountered an issue with ninja and VS2013 when using versions of > CMake prior to 2.8.12.1. This isn't a combination that we typically use so > we've not run into it previously in our own builds. It isn't specifically > tied to upgrading the minimum version as it's a

I hope this problem hasn't been posted before, I cannot find a way to search the archives... I use rsync successfully between several Suse 9.1 machines at my work - never with any problem(s). I had to move my email from an obscure mail client (that saves each message as a separate file) to Mozilla mail (for security purposes). So, my "old" program that I used to sync my mail