similar to: Supporting sub commands in LLVM command line tools

Not sure I follow how this would work. "llvm" is an executable, and "opt" is a symlink to "llvm"? How does llvm then detect that it needs to use the opt set of commands? That said, in principle sure you could have "llvm opt <opt-specific command syntax>" or "llvm llc <llc options>". At some point you'd probably need to extend

On 18 June 2016 at 02:58, Mehdi Amini via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I haven't looked at the implementation, but conceptually this looks nice! Indeed, really nice! > We talked internally about an option to build something like a single "llvm" > binary that would be symlinked by opt/llc/etc. So that when you invoke > `opt`, it would run the

Hi Zach (or anyone else who may have a clue), I'm currently investigating making use of LLVM for PDB parsing for with a view to supporting partial PDBs as produced by /DEBUG:FASTLINK as the VS DIA SDK hasn't been updated to handle them. I know this is probably low on your priority list but since /DEBUG:FASTLINK is now the implied default for VS2017 I figure it's a good time to take a

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

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

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

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

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

Trunk clang does not pass CMake C Compiler test like below: CMake Error at /home/usr4/c74014i/opt/cmake-3.16.3-Linux-x86_64/share/cmake-3.16/Modules/CMakeTestCCompiler.cmake:60 (message): The C compiler "/home/usr4/c74014i/opt/clang/current/bin/clang" is not able to compile a simple test program. It fails with the following output: Change Dir:

Hi All, As a part of a recent move of libFuzzer from LLVM to compiler-rt I am looking into updating the build code for the libraries which use libFuzzer. I have looked into tools/llvm-pdbutil, and “ninja llvm-pdbutil-fuzzer” does not build at all, and the error refers to non-existent headers. The last update to the codebase is reasonably recent, and was done in June 2017. Is anyone using it?

I see many tests that are prefixed with "requires: shell". A quick search over the codebase shows 101 tests that contain this directive. This basically means there are 101 tests that say "I don't support running on Windows". I would like to get this number to 0. Ironically, many of these tests can be made to run on Windows simply by removing the requires: shell line.

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

Hi, If there is no blocker (James?), we should be able to move on, so I filed as a starter: https://reviews.llvm.org/D25710 <https://reviews.llvm.org/D25710>: [Doc] Drop MSVC2013 support — Mehdi > On Oct 12, 2016, at 4:03 PM, Reid Kleckner <rnk at google.com> wrote: > > I migrated the sanitizer-windows builder to VS 2015, and it went green here: >

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

I'm just wondering if anyone's using Ninja (which buffers output from subcommands, such as lit/FileCheck/etc) & has thought about/found a way to force FileCheck to use colour in spite of Ninja's buffering. Thanks, - David

Hi. Failure 1: Current clang-6.0 from http://apt.llvm.org/, current sources. $ CC=clang-6.0 CXX=clang++-6.0 cmake -DLLVM_ENABLE_PROJECTS="clang;libcxx;libcxxabi;compiler-rt;lld;polly;openmp" -DLLVM_USE_SANITIZER="Address;Undefined" -DCMAKE_BUILD_TYPE=Release -GNinja ../llvm $ ninja [200/3921] Building Attributes.gen... FAILED: include/llvm/IR/Attributes.gen.tmp cd

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:

Hi, This might be interesting since it seems to be the only LLVM test failing with VS 2015: FAIL: LLVM :: DebugInfo/PDB/pdbdump-symbol-format.test (7377 of 14212) ******************** TEST 'LLVM :: DebugInfo/PDB/pdbdump-symbol-format.test' FAILED ******************** Script: -- llvm-pdbdump -symbols C:\cygwin64\home\ismail\src\llvm\test\DebugInfo\PDB/Inputs/symbolformat.pdb |

Hey Guys, I'm working on a project in Android related to System-level Audio DSP Effects for Tuning Android Audio. I want to leverage Faust ( https://faust.grame.fr/) to allow users to program their own filters. Faust provides a libfaust implementation which includes a JIT Compiler which leverages LLVM and seems to be the best path for me to use. Unfortunately I'm having problems

What makes the reports not actionable on windows? On Tue., 22 Aug. 2017, 3:49 pm Reid Kleckner via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I think we should delete it. David implemented it a long time ago when he > was working on llvm-pdbdump, but he's moved on. Zach was never able to use > it effectively because he works on Windows, so the reports were not >