similar to: How to debug passes

Displaying 20 results from an estimated 2000 matches similar to: "How to debug passes"

2019 Sep 18
2
How to debug passes
Iulia, You need to check the contents of the hello.ll (or hello.bc) file rather than the input *.c file - ultimately that's what opt consumes. Try compiling without any optimisations: clang -O0 -emit-llvm -S hello.c -c -o hello.ll -Andrzej On 18/09/2019 11:34, iulia_s24 wrote: > Hi, > > Actually I copy-pasted step 5 from the article in which I found the > solution, in the text
2019 Sep 18
2
How to debug passes
> opt -load lib­dum­my­pass.so -dum­my­pass hel­lo.ll Looks like you are loading a shared library different from "LLVMHello.so". did you change the name of the compilation unit from "Hello.cpp" into "dummypass.cpp"? (As asked previously by Andrzej) did you register the dummy pass? > RegisterPass<DummyPass> X("dummypass",
2015 Dec 16
2
LLVM and parallelization
Hi, I know LLVM provides thread-level automatic parallel support using OpenMP (see  http://blog.llvm.org/2015/05/openmp-support_22.html), but it is not clear for me which of the following is correct? 1. Clang inserts in the source code OpenMP compiler directives, so, it auto-parallelizes the serial source code provided as input or2. Clang can compile manually written parallel source code that uses
2017 Jun 05
2
Question
Hello, 1. Can you please tell me how can I find the type of my Intel Xeon?I see in LLVM code that Intel Xeon processors can be of type "core2", "penryn", "westmere", "skylake". 2. I also see that "skylake" can be a type and a subtype as well.How can I find out the subtype of my architecture? Looking forward for you answer. Thank you.Iulia On
2015 Dec 16
2
Instruction scheduling done before or after register allocation
Hi, I have read the steps of code generation from here: The LLVM Target-Independent Code Generator — LLVM 3.8 documentation |   | |   | |   |   |   |   |   | | The LLVM Target-Independent Code Generator — LLVM 3...Instruction Selection Instruction Selection is the process of translating LLVM code presented to thecode generator into target-specific machine instructions. | | | | View on llvm.org
2019 Sep 10
3
Question about using multiple functions in a Function pass
Hi all, I would want to know if from the runOnFunction method of a Function pass, other functions in IR, except for the one received as parameter, can be obtained as well, from a call instruction, as follows: Function F = dyn_cast<Function>(callInst); Or do I need a Module pass to work in IR with multiple functions from input source code? If so, it is accepted to have O(n^3) complexity in a
2017 Jun 05
2
Build problems
Hello, Could someone please tell me why LLVM and clang downloaded from here: svn co http://llvm.org/svn/llvm-project/llvm/trunk llvmsvn co http://llvm.org/svn/llvm-project/cfe/trunk clang and generated using cmake: cmake -G "Visual Studio 15 2017" ../llvm does not compile in Visual Studio? I am using Batch Build in Visual Studio and I have selected only ALL_BUILD project to build as
2019 Sep 03
2
Get constants of undefined types in IR
Hi Tim, My mistake not including the llvm-dev, excuse me. affinityElement.__bits[0] worked fine for me, thank you. I am new in using the API for Constants and I am facing the error "incomplete type is not allowed" on the last last of below code: Type * ET = IntegerType::getInt64Ty(I.getContext()); unsigned long size = cpuAffinityVector.size(); ArrayType * AT = ArrayType::get(ET,size);
2019 Aug 31
3
Get constants of undefined types in IR
Hello all, I would like to obtain a constant that is initialized with a value of type cpu_set_t, a type which is defined by Pthreads. The problem is that a variable of this type cannot be cast to an int value, even in C source code. I tried get methods from Constant or ConstantInt classes, but with no result. How can I obtain such constant object in IR? Thank you, Iulia -------------- next
2017 Jun 05
2
Question
Can you also please tell me how can I find out the ABI (application binary interface)? Thanks,Iulia On Monday, June 5, 2017 8:58 PM, Bruce Hoult <bruce at hoult.org> wrote: grep name /proc/cpuinfo Then look up the model number in https://en.wikipedia.org/wiki/List_of_Intel_Xeon_microprocessors On Mon, Jun 5, 2017 at 8:41 PM, Iulia Stirb via llvm-dev <llvm-dev at
2017 Jun 04
2
Question
Hello, Could someone please answer the following question: Does LLVM support code generation for Intel Processors? Which Intel processors are supported? I am interested especially in Intel Xeon Processor, but you can give me information about the others as well. Thank you,Iulia -------------- next part -------------- An HTML attachment was scrubbed... URL:
2017 Jun 06
2
Question
Thank you. So the ABI in llvm will be "gnu" for all Linux distributions? On Monday, June 5, 2017 11:39 PM, Tim Northover <t.p.northover at gmail.com> wrote: On 5 June 2017 at 11:54, Iulia Stirb <iulia_s24 at yahoo.com> wrote: > Can you also please tell me how can I find out the ABI (application binary > interface)? Could you send your messages with a smaller
2017 May 06
2
LLVM and Pthreads
Hello, I know clang supports -pthread option (here). Does this mean I can call pthread routines inside llvm code and which pthread library is used, the one for Linux OS or the one for Windows? Thank you.Iulia -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170506/7a201a40/attachment.html>
2020 Jun 12
2
[flang-dev] [cfe-dev] [RFC] Refactor Clang: move frontend/driver/diagnostics code to LLVM
For those of us not familiar with clang internals, it would be helpful if you could describe the parts of clang that you're considering sharing and explain what existing code they would replace in flang (if any) and what benefits we gain by sharing them. In particular, these were mentioned previously: DiagnosticsEngine, SourceManager, SourceLocation, FileManager, VFS Thanks, Tim On
2020 Jun 11
2
[cfe-dev] [flang-dev] [RFC] Refactor Clang: move frontend/driver/diagnostics code to LLVM
On 6/11/20 4:04 PM, James Y Knight wrote: > I think the expectation is that LLVM remains at the bottom of the > dependency tree, with frontend-support depending on LLVM, and Clang and > Flang depending on frontend-support (and LLVM). > > Not everything which makes sense to share between clang and flang makes > sense to be part of llvm core. E.g., implementation of a
2019 Jul 15
3
Looking for an out-of-source "Hello, world" LLVM/Clang pass example
Andrzej, On 7/14/19 8:02 AM, Andrzej Warzynski wrote: > This is still very early stages, but you can be my guinea pig: > > https://github.com/banach-space/llvm-tutor > > It's a tutorial that I've been preparing recently and am hoping to > present somewhere at some point :-) I believe that it already covers 1), > 2) and 3). I haven't had the time to work on 4).
2020 Jun 11
2
[flang-dev] [RFC] Refactor Clang: move frontend/driver/diagnostics code to LLVM
On 6/11/20 3:32 AM, Andrzej Warzynski wrote: > > > On 11/06/2020 00:49, Michael Kruse wrote: >> Am Mi., 10. Juni 2020 um 10:04 Uhr schrieb Doerfert, Johannes via >> flang-dev <flang-dev at lists.llvm.org>: >>> I'm not against a subproject *but* if we also move the existing >>> llvm/lib/Frontend stuff, that would introduce a dependence from
2020 Oct 08
2
[cfe-dev] Upcoming upgrade of LLVM buildbot
Hi Paula, This error is fine. The buildbot has tested the worker version. 0.8.x apparently does not have that method. The error gets handled gracefully on the server side. At least it seems so so far. That should not prevent your bot from connecting. Thanks Galina On Thu, Oct 8, 2020 at 2:11 PM Paula Askar <paulatoth at google.com> wrote: > Hey Andrzej, > > What are you seeing
2017 Jun 08
2
Question
I want to cross-compile using clang and I have to specify the following triple: <arch><sub>-<vendor>-<sys>-<abi>I know that sub-architectures ("sub" in the triple) for x86_64 Intel Xeon processors could be v2 for ivy bridge or v3 for haswell or v4 etc. Could you please answer: which version of sub-architecture is considered sandy bridge for Intel® Xeon®
2019 Sep 08
2
New PM, opt and command line options
Hi all, I'm porting some LLVM plugins to the new pass manager and I've noticed that the command line options are no longer registered when using `-load-pass-plugin` (the new PM flag) to load the plugins in opt. Everything is back to normal when loading via `-load` (the legacy PM). For example, given this CL option: static cl::opt<bool> SomeFlat("some-flag",