search for: malea

Hello Daniel, thank you very much for the clarification. I confirm that the two libraries showed up without specifying the two configure flags. Cheers, Alberto On Fri, Mar 30, 2012 at 8:48 PM, Malea, Daniel <daniel.malea at intel.com> wrote: > Hi Alberto, > > I can confirm the problem you mentioned, and will look at fixing it. You have indeed stumbled on a bug; the two libraries mentioned should only be required if you build with profiling enabled (--enable-intel-jitevents --ena...

...and line-number information correctly but I can't seem to get it to work with lldb. If anyone can take a look at it and suggest what I'm doing wrong or suggest tools that I can use to debug this problem - I'd greatly appreciate it. Best, .Chris. On Apr 23, 2013, at 6:32 PM, "Malea, Daniel" <daniel.malea at intel.com> wrote: > I built SVN revision 180023, looks like it's slightly newer than yours: > > LLVM (http://llvm.org/): > LLVM version 3.3svn > DEBUG build with assertions. > Built Apr 22 2013 (14:26:17). > Default target: x86_64-...

...eem to get it to work with lldb. > > If anyone can take a look at it and suggest what I'm doing wrong or suggest tools that I can use to debug this problem - I'd greatly appreciate it. > > Best, > > .Chris. > > > > > On Apr 23, 2013, at 6:32 PM, "Malea, Daniel" <daniel.malea at intel.com> wrote: > >> I built SVN revision 180023, looks like it's slightly newer than yours: >> >> LLVM (http://llvm.org/): >> LLVM version 3.3svn >> DEBUG build with assertions. >> Built Apr 22 2013 (14:26:17). &gt...

Hi Alberto, I can confirm the problem you mentioned, and will look at fixing it. You have indeed stumbled on a bug; the two libraries mentioned should only be required if you build with profiling enabled (--enable-intel-jitevents --enable-oprofile flags to configure, or "-DUSE_INTEL_JITEVENTS -DUSE_OPROFILE" flags to cmake.) A workaround, for the time being, would be to ignore those

>Since MCJIT works on x86, please don't remove it from the supported >platforms list. One downside of using the macro trick is that the test names >are still printed even when they are disabled. It sounds like you need to >modify the macro to also check for the target triple as well... This was just a temporary change to see how it works. >There isn't anything in MCJIT as

On 2013-03-13 3:15 AM, "Jyotsna Verma" <jverma at codeaurora.org> wrote: > >I noticed "TARGET_HAS_JIT" flag in Makefile.config. Can I use this flag to >exclude MCJIT and JIT tests when not set? This will be a simpler change >than >modifying the macro. > >Thanks, >Jyotsna TARGET_HAS_JIT seems to be an autoconf thing (also, not really sure how it

Hi all, I am experiencing a problem with the libraries IntelJITEvents and OProfileJIT They are listed in the `llvm-config --libs all` output but they are not present in the lib install directory. I am using git, revision 153741. Am I missing something ? Is this a known issue ? Thanks, Alberto

Hi Jyotsna, Currently there's a preprocessor trick that prevents llvm/unittests/ExecutionEngine/MCJIT tests from running on architectures and operating systems that are known to fail. Specifically, check out the functions OSSupportsMCJIT() and ArchSupportsMCJIT() functions in unittests/ExecutionEngine/MCJIT/MCJITTestBase.h, and the corresponding macro SKIP_UNSUPPORTED_PLATFORM that is used

Hi There, We want to disable all ExecutionEngine JIT/MCJIT tests (llvm/unittests/ExecutionEngine) for Hexagon. I have been looking into the test framework but haven't quite figured out how to turn them off. We cross compile Hexagon on X86 and are not interested in JIT support. Thanks, Jyotsna -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux

...existing RuntimeDyldMachO) which implements the dynamic loading of the ELF image into memory, its relocation and execution. 3. An implementation of a MC-JIT - GDB bridge which allows to fully debug the JITted code with GDB. These patches will be a superset of an earlier patch sent by Daniel Malea (http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20111219/133702.html). We'll be very happy to have the patches reviewed, and see a functional MC-JIT implementation for ELF in LLVM trunk soon. Eli --------------------------------------------------------------------- Intel Israel (7...

.... If not, then we can probably enable them only when Host and Target Triples are same and the host architecture is in the supported list. Thanks, Jyotsna -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation >-----Original Message----- >From: Malea, Daniel [mailto:daniel.malea at intel.com] >Sent: Monday, March 11, 2013 2:52 PM >To: Jyotsna Verma; llvmdev at cs.uiuc.edu >Subject: Re: [LLVMdev] Disabling ExecutionEngine tests for Hexagon > >Hi Jyotsna, > >Currently there's a preprocessor trick that prevents >llvm/un...

Daniel, I didn't find the MCJIT directory under unitests/ExecutionEngine ... there is only a directory called JIT. You mean this directory ? Many thanks --Armin Malea, Daniel wrote: > Take a look at the MCJIT unit tests under unittests/ExecutionEngine/MCJIT > > The MCJITTestBase class does the majority of the interactions with the LLVM API you're referring to. > > Good luck, > Dan > > On 2012-10-13, at 4:57 AM, "Armin Steinhoff&q...

Hi, I notice you're running a 32-bit program; are you also on a 32-bit host, or do you have a 64-bit OS installed? We don't generally test on 32-bit hosts, so it's possible you found a new bug. In addition, there are some known bugs with debugging 32-bit programs (even on 64-bit hosts) which will we hopefully be resolving soon. Nonetheless, I was unable to reproduce the behaviour you

I believe the perf tool cannot profile/analyze the JITed code in MCJIT model. Can you please confirm this ? I was working on a patch to fix this. Another question, is the there any support to map the llvm IR with x86 generated assembly ? so its easier to analyze the code generator. -------------- next part -------------- An HTML attachment was scrubbed... URL:

Sorry if asked before. I'm new to LLDB, try to use it according to the lldb project site. I write some very simple code like: #include <stdio.h> int main(int argc, char **argv) { int counter = 0; while ( counter < 10 ) counter++; printf("counter: %d\n", counter); return 0; } and the session like: $ clang -g main.c $ lldb-3.4 a.out (lldb)

...2, Armin Steinhoff <as at steinhoff-automation.com> wrote: > Daniel, > > I didn't find the MCJIT directory under unitests/ExecutionEngine ... there > is only a directory called JIT. > You mean this directory ? > > Many thanks > > --Armin > > > > > Malea, Daniel wrote: >> >> Take a look at the MCJIT unit tests under unittests/ExecutionEngine/MCJIT >> >> The MCJITTestBase class does the majority of the interactions with the >> LLVM API you're referring to. >> >> Good luck, >> Dan >> >>...

Hmm, are you using a version of LLVM with asserts enabled (I.e. A debug build)? I cut-and-paste your IR into a text file and ran (a debug version of) llc on it, which caused the following assertion failure that seems related to some DWARF mishap: llc: ../lib/CodeGen/AsmPrinter/DwarfDebug.cpp:1400: void llvm::DwarfDebug::beginFunction(const llvm::MachineFunction*): Assertion `TheCU &&

Looks like a bug in the DebugIR pass. I imagine that without the -debug–ir flag, you will be able to get a little further. Nonetheless, can you send me the "bitcodetestqtapp" that you're running, or steps to reproduce? I'd love to take a look. Thanks, Dan From: Shailesh Kumar <shaileshkumar41 at yahoo.com<mailto:shaileshkumar41 at yahoo.com>> Reply-To: Shailesh

Hi all, are there any plans to correct/implement the "getPointerToGlobal()" method for accessing global variables that are emitted by MCJIT? (see for details the unit test of MCJIT) Best Regards Armin

As far as I know, no one is working to fix the test case in question. Patches welcome :) Cheers, Dan On 2012-11-13, at 1:29 AM, "Armin Steinhoff" <armin at steinhoff.de> wrote: > > Hi all, > > are there any plans to correct/implement the "getPointerToGlobal()" method for accessing global variables that are emitted by MCJIT? > (see for details the