similar to: [LLVMdev] DebugInfo/PDB/pdbdump-symbol-format.test fails with VS 2015

FWIW, this test is passing for me on Windows 7 with Visual Studio 2015 (debug build). 59> Running all regression tests 59> -- Testing: 23734 tests, 32 threads -- 59> 59> Testing Time: 634.19s 59> Expected Passes : 22821 59> Expected Failures : 160 59> Unsupported Tests : 753 59> lit.py: lit.cfg:195: note: using clang:

Ok just tried on Win 7 and the same problem occurs. I am building with : cmake -G "Ninja" -DCMAKE_BUILD_TYPE=Release -DLLVM_USE_CRT_RELEASE=MT -DLLVM_ENABLE_TIMESTAMPS=ON -DLLVM_ENABLE_ASSERTIONS=ON -DLLVM_INSTALL_TOOLCHAIN_ONLY=ON -DLLVM_TARGETS_TO_BUILD="ARM;X86" -DPYTHON_EXECUTABLE=$python_exe -DLLVM_BUILD_TESTS=ON -DLLVM_LIT_TOOLS_DIR=C:/cygwin64/bin fwiw compiler-rt is

I came across a PDB that caused llvm-pdbdump to crash. I tracked it down to a missing overload for a data type in the variable printer. When I tried to provide an implementation, I discovered that there were some bugs in the existing overloads and it was easy to come up with combinations of types that weren't being dumped right. I created some test cases and tried to fix these problems but

Thank you for responding to my problem I have no problem building in Debian 8 , the problem is with Cygwin64 I see that the two lines from Cygwin64 >> gcc -g -O2 -Wall -Wsign-compare usbhid-ups.c -o usbhid-ups In file included from usbhid-ups.c:32:0: And Debian>>> make[1]: Entering directory '/home/walter/nut/drivers' depbase=`echo usbhid-ups.o | sed

On Tue, Jul 26, 2016 at 12:30 PM, Zachary Turner <zturner at google.com> wrote: > I wrote most of the pdb code in llvm so far. As Reid suggested, if you > look in DebugInfo/PDB/Raw there is a significant amount of code dealing > with msf files and raw pdb streams. If you build the llvm-pdbdump tool you > can run it with the "raw" subcommand to dump lots of low level

libusb do you have installed >>> 1.2.6.0-2 ./configure --with-drivers=usbhid-ups Configuration summary: ====================== build serial drivers: yes build USB drivers: yes build SNMP drivers: no build neon based XML driver: yes enable Avahi support: no build Powerman PDU client driver: no build IPMI driver: no build Mac OS X meta-driver: no build i2c based drivers: no enable SSL

Hi folks, I'm hitting the below assertion failure when compiling this small piece of C code (repro.c, attached). My command line is: bin/clang --target=aarch64-linux-gnu -c -O2 repro.c clang is built from top of trunk as of this morning. It only happens at -O2, and it doesn't happen with the default target (x86_64). I tried to reproduce using just 'llc -O2' but didn't

Hi R package developers. This is literally the strangest thing I've ever seen. Latest (as of a month ago) R under cygwin64. I'm teaching an intern package building and using the .C interface. The package compiles, but when it gets to "setting up lazy load" or some such it throws the error "triang" not available for .C() in package "randpkg". Upon checking,

Thanks for notifying me. Yes, this was a recent change. Taking a look now. On Wed, Jul 20, 2016 at 1:49 PM, Michael Kuperstein <mkuper at google.com> wrote: > +Sanjay, who touched this last. :-) > > On Wed, Jul 20, 2016 at 12:44 PM, Ismail Badawi (ibadawi) via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> Hi folks, >> >> I'm hitting the

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

Sanjay: let me know if this is something that will apply to 3.9. Thanks, Hans On Wed, Jul 20, 2016 at 5:59 PM, Sanjay Patel via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Quick update - the bug existed before I refactored that chunk in > InstSimplify with: > https://reviews.llvm.org/rL275911 > > In fact, as discussed in https://reviews.llvm.org/D22537 - because we have a

The new error message is: llvm-pdbdump: DIA Error: An unknown error has occurred. HRESULT: 0x800700C1: Calling NoRegCoCreate which is more or less what I expected. The specific HResult is kind of interesting, it maps to "msdia140.dll is not a valid Win32 application". I don't know if this means that it can't find the DLL, or that it did find the DLL and it's corrupt. Is

We can try to print a better error message here, but it looks like regardless someone will need physical access to the bot to determine what the problem is with DIA. On Wed, Oct 19, 2016 at 8:51 AM Reid Kleckner <rnk at google.com> wrote: > I filed https://llvm.org/bugs/show_bug.cgi?id=30736 to get that fixed. > > On Wed, Oct 19, 2016 at 3:52 AM, Briltz, Denis <Denis.Briltz at

Sure. David, what do you think about merging this to 3.9? Sanjay: are you saying I'd just apply that diff to InstructionSimplify.cpp, not InstCombineSelect.cpp? On Fri, Jul 22, 2016 at 7:08 AM, Sanjay Patel <spatel at rotateright.com> wrote: > Hi Hans - > > Yes, I think this is a good patch for 3.9 (cc'ing David Majnemer as code > owner). The functional change was

Hello, Say the original type is Integer i16*,&nbsp; I want to create a v16i16* type to replace it. static Type *getVectorPtr(Type *Ty) { &nbsp; &nbsp; PointerType *PointerTy = dyn_cast<PointerType&gt;(Ty); &nbsp; &nbsp; assert(PointerTy &amp;&amp; "PointerType expected"); &nbsp; &nbsp; unsigned addSpace = PointerTy-&gt;getAddressSpace();

Hi, “clang-x64-ninja-win7” was switched to VS2015. It is red now due to a few PDB tests and one sanitizer test. Failing Tests (10): LLVM :: DebugInfo/PDB/DIA/pdbdump-flags.test LLVM :: DebugInfo/PDB/DIA/pdbdump-linenumbers.test LLVM :: DebugInfo/PDB/DIA/pdbdump-symbol-format.test LLVM :: tools/llvm-pdbdump/class-layout.test LLVM :: tools/llvm-pdbdump/enum-layout.test

David, Sanjay: ping? On Mon, Jul 25, 2016 at 11:07 AM, Hans Wennborg <hans at chromium.org> wrote: > Sure. David, what do you think about merging this to 3.9? > > Sanjay: are you saying I'd just apply that diff to > InstructionSimplify.cpp, not InstCombineSelect.cpp? > > On Fri, Jul 22, 2016 at 7:08 AM, Sanjay Patel <spatel at rotateright.com> wrote: >> Hi

LGTM On Wednesday, July 27, 2016, Hans Wennborg <hans at chromium.org> wrote: > David, Sanjay: ping? > > On Mon, Jul 25, 2016 at 11:07 AM, Hans Wennborg <hans at chromium.org > <javascript:;>> wrote: > > Sure. David, what do you think about merging this to 3.9? > > > > Sanjay: are you saying I'd just apply that diff to > >

On Fri, Jan 15, 2016 at 11:05 AM, Ismail Donmez <ismail at i10z.com> wrote: > Hi, > > On Fri, Jan 15, 2016 at 12:59 AM, Chris Bieneman <beanz at apple.com> wrote: >> I’m kinda scared that you’re using it. What are you trying to accomplish >> that you are using it? Generally having LLVM split among that many >> dynamically loaded libraries results in

----- Original Message ----- > From: "Renato Golin" <renato.golin at linaro.org> > To: "İsmail Dönmez" <ismail at donmez.ws> > Cc: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> > Sent: Wednesday, March 26, 2014 8:14:18 AM > Subject: Re: [LLVMdev] Lots of regtest failures on PPC64/Linux > > Hi Ismail, > > Is