similar to: Core dump Compiling with clang sample

I'm trying to add a new option to clang to enable my auto profile pass. I've added this to Options.td and Driver/Tools.cpp, but I'm not getting the option -auto-profile in cc1's invocation. I've checked that the code to push -auto-profile is executed, but if use -v, I don't see -auto-profile in the cc1 invocation. Can anyone point me to some document that explains how to

You are calling the option -auto-profile in some places and -fauto-profile in others. Maybe it is just a typo? On 1 October 2013 15:31, Diego Novillo <dnovillo at google.com> wrote: > I'm trying to add a new option to clang to enable my auto profile > pass. I've added this to Options.td and Driver/Tools.cpp, but I'm not > getting the option -auto-profile in cc1's

Ferret throws a bus error in the unit tests under Solaris, sun4u architecture. http://ferret.davebalmain.com/trac/ticket/272 Bug reporter appears to be on Solaris 8 with Ruby 1.8.4. I''ve tried on Solaris 10 (first release and 10/06, first without and then with the most recent patch set), both with Ruby 1.8.6, and get exactly the same error in the same spot. Tried with 0.11.4 and also

I upgraded from Samba 3.0.20 to 3.0.21a last night on my Solaris 10 machine. After the upgrade, everything seemed to work fine, but I see that Samba is panic'ing in the logs. As far as I can tell, the client retries whatever it was doing and succeeds (at least, we've had no reports of problems from our users). I have attached a level 10 debug, backtrace, and my smb.conf. The

We have an application that allows the user to compile and execute C++ code on the fly, using Orc JIT v2, via the LLJIT class. And we would like to extend it to allow the user to provide CUDA source code as well, for GPU programming. But I am having a hard time figuring out how to do it. To JIT compile C++ code, we do basically as follows: 1. call Driver::BuildCompilation(), which returns a

Dear LLVM developers, Our team has developed an LLVM-based protection mechanism that (i) prevents control-flow hijack attacks enabled by memory corruption errors and (ii) has very low performance overhead. We would like to contribute the implementation to LLVM. We presented this work at the OSDI 2014 conference, at several software companies, and several US universities. We received positive

Sound right now like you are emitting an LLVM module? The best strategy is probably to use to emit a PTX module and then pass that to the CUDA driver. This is what we do on the Julia side in CUDA.jl. Nvidia has a somewhat helpful tutorial on this at https://github.com/NVIDIA/cuda-samples/blob/c4e2869a2becb4b6d9ce5f64914406bf5e239662/Samples/vectorAdd_nvrtc/vectorAdd.cpp and

I have made a bit of progress... When compiling CUDA source code in memory, the Compilation instance returned by Driver::BuildCompilation() contains two clang Commands: one for the host and one for the CUDA device. I can execute both commands using EmitLLVMOnlyActions. I add the Module from the host compilation to my JIT as usual, but... what to do with the Module from the device compilation? If I

On Tue, Oct 1, 2013 at 3:53 PM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: > The option handling in clang in fairly different from opt. The comment > about the mixed name was just a guess as to why you don't see the > driver passing it down to -cc1. Clang::ConstructJob is ~2k lines long. I was putting the handling of this option too far down. I moved it up and

Hi there, I'm using clang to cross compile for cortex-m3. I eventually managed to do so with clang++ -ccc-gcc-name arm-none-linux-gnueabi-g++ -ccc-host-triple thumbv7m-none-gnueabi source.cpp -c -mcpu=cortex-m3 I would like to understand what -ccc-gcc-name does exactly and how can I get ride of it? >From what I understand, it's needed by the driver in order to find the binutils for

I recently patched my Solaris server and suddenly my Samba service is not working correctly. When Anyone accesses a samba share the samba daemon panics and shuts down. Solaris than restarts the system, unless there are multiple panics simultaneously than the service is placed in maintenance mode. The SAMBA server is a stand alone supporting a dozen end users for a large file store behind the

The option handling in clang in fairly different from opt. The comment about the mixed name was just a guess as to why you don't see the driver passing it down to -cc1. Once that is working, you will probably need to: * Patch ParseCodeGenArgs to record the option * Patch EmitAssemblyHelper::CreatePasses to set the option to enable the pass in the pass manager (assuming that is the effect

On Tue, Oct 1, 2013 at 4:51 PM, Diego Novillo <dnovillo at google.com> wrote: > On Tue, Oct 1, 2013 at 3:53 PM, Rafael Espíndola > <rafael.espindola at gmail.com> wrote: >> The option handling in clang in fairly different from opt. The comment >> about the mixed name was just a guess as to why you don't see the >> driver passing it down to -cc1. > >

Heres my full code listing, im totally stuck. // Whistle.cpp : Defines the entry point for the console application. // #include "stdafx.h" #include "clang/CodeGen/CodeGenAction.h" #include "clang/Driver/Compilation.h" #include "clang/Driver/Driver.h" #include "clang/Driver/Tool.h" #include

Making a symlink to clang in the same directory as the GCC / binutils (I'll call it $ARM_BIN) called arm-none-linux-gnueabi-clang (and one with clang++ too) and another link in the $ARM_BIN/../lib directory to clang directory located under clang's lib (for includes) should be enough. Gordon Keiser Software Development Engineer Arxan Technologies gkeiser at arxan.com www.arxan.com 

On Tue, Oct 1, 2013 at 3:42 PM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: > You are calling the option -auto-profile in some places and > -fauto-profile in others. Maybe it is just a typo? In opt, the option is named '-auto-profile' when I instantiate the pass: INITIALIZE_PASS(AutoProfile, "auto-profile", "Auto Profile loader", false,

I tried what you said, now I get: LLVM ERROR: Program used external function 'yipee' which could not be resolved! Stack dump: 0. Running pass 'X86 Machine Code Emitter' on function '@main' did not even get as far as a breakpoint. Óscar Fuentes wrote: > > gafferuk <gafferuk at gmail.com> writes: > >> Im confused. The function i wish to call is

gafferuk <gafferuk at gmail.com> writes: > Im confused. The function i wish to call is a return type of int. > Im calling it with int dd = yipee(1); > > What's wrong? Declare the function: int yipee(int); int main() { int dd = yipee(1); return 0; } If that still crashes, put a breakpoint on `yipee' and see if the execution gets there, if the argument is

Hi, I'm not sure if this is a libclang, llvm::cl or clang-interpreter issue so I'll try posting here for a response. I am using libclang as a frontend to the LLVM JIT (3.3 release). I started from the clang-interpreter example and have everything working (given a C/C++ source file I can have it JIT'd to memory and executed) for a single run. When I try to compile a second source

On Thu, Jun 4, 2015 at 5:33 PM, Reid Kleckner <rnk at google.com> wrote: > On Thu, Jun 4, 2015 at 5:17 PM, Teresa Johnson <tejohnson at google.com> wrote: >> >> Agreed. Although I assume you mean invoke the new pass under a >> ThinLTO-only option so that avail extern are not dropped in the >> compile pass before the LTO link? > > > No, this pass